Supplier intelligence · Acquiry Labs
Who actually supplies this brand?
A buyer can recognise the same checkout on ten shops and still have the wrong software supplier on its shortlist.
- Research Lead
- Joash Boyton
- Research edition
- 1.0
- Published
- 13 November 2026
- Companion dataset
- Provider map, edition 1.1
What did Joash investigate?
Whether a checkout shared by 10 shops shows who supplies their commerce software. He began with a real disclosure, Stripe and Squarespace, then tested the counting rule on a fictional retail case.
What changed for the buyer?
Arc fell from 10 shops initially counted to 3 supported. The buyer’s top three moved from Arc, Birch, Cove to Birch, Cove, Dune. Dune climbed from 4th to 3rd without adding a shop.
How can I check it?
Open the original disclosure, apply the correction yourself, then rerun the numbers with the public fixture and verify.py. Every file has a published checksum.
Public evidence
Read the relationship one role at a time.
Squarespace is the merchant-facing brand. Stripe describes the infrastructure it provides underneath the payments experience.
- Brand
- Squarespace introduced its branded payments offering in 2023.
- Supplier
- Stripe identifies Connect and Payments as infrastructure for Squarespace merchants. Original source: Stripe Squarespace case study (opens in a new tab)
- Evidence
- The disclosure comes from a party to the relationship. A copy of that account has the same origin.
| Dataset record | Squarespace and Stripe, Squarespace Payments |
|---|---|
| Role in the map | Embedded infrastructure |
| Time scope | Branded rollout began in 2023 |
| What the dataset records | Stripe says its Connect and Payments products provide payments infrastructure for Squarespace merchants. Squarespace launched its branded payments offering in 2023. |
| Evidence checked | 13 November 2026 |
What belongs in a buyer memo?
“Stripe identifies a payments infrastructure relationship with Squarespace.” Put the source, date and role beside the statement so a reader can audit it.
What still needs separate evidence?
The merchant’s legal counterparty, exclusivity, customer-level revenue and the identity of a particular shop’s commerce software supplier. A visible checkout alone does not settle those questions.
Scope of the real example: the source supports an infrastructure role. The ten shops and all four suppliers in the example below are fictional.
Read Stripe’s case study (opens in a new tab)Inspect the Squarespace rowOpen dataset edition 1.1
Worked example · synthetic
One correction changes the third call.
Synthetic retail teaching case: the ten shops and four suppliers are fictional and describe no real company.
A buyer ranks commerce software suppliers by distinct supported shops. An analyst initially credits Arc for every shop showing a shared checkout. A correction establishes that the checkout identifies a payments provider. 3 shops have separate records supporting Arc.
- shops initially counted
- 10
- links still supported
- 3
- links left open
- 7
Initial shortlist: Arc, Birch, Cove.
The evidence that survives
All 10 shops show the shared checkout. The analyst counted all 10 for Arc. Apply the correction to see which links hold.
- S01Counted
- S02Counted
- S03Counted
- S04Counted
- S05Counted
- S06Counted
- S07Counted
- S08Counted
- S09Counted
- S10Counted
What it does to the shortlist
Initial order shown. The corrected order appears when you apply the correction.
| Rank | Supplier | Shops counted | What changed |
|---|---|---|---|
| 1 | Arc | 10 | Flagged: the analyst counted every shop with the shared checkout. That was a mistake. |
| 2 | Birch | 8 | Stipulated count |
| 3 | Cove | 6 | Stipulated count |
| 4 | Dune | 4 | Stipulated count |
What changes for the buyer? On this criterion, the buyer calls Birch, Cove and Dune first. Arc remains a prospect. New shop-level evidence could move it back up.
Both states, in plain tables
The same before and after, with no buttons or scripts. These tables are part of the page, and they are what prints.
Both shortlists
| Rank | Initial shortlist | Corrected shortlist |
|---|---|---|
| 1 | Arc | Birch |
| 2 | Birch | Cove |
| 3 | Cove | Dune |
The ranking, before and after
| Fictional supplier | Initial count* | Corrected | Rank movement |
|---|---|---|---|
| Arc | 10 | 3 | 1st to 4th |
| Birch | 8 | 8 | 2nd to 1st |
| Cove | 6 | 6 | 3rd to 2nd |
| Dune | 4 | 4 | 4th to 3rd |
*The initial count reproduces the analyst’s mistake. Other suppliers’ counts are stipulated in this exercise. Rank by count descending, then supplier name ascending.
The ten shops
| Shop | Shared checkout | Independent platform record for Arc | After the correction |
|---|---|---|---|
| S01 | Yes | Yes | Supported |
| S02 | Yes | Yes | Supported |
| S03 | Yes | Yes | Supported |
| S04 | Yes | No | Unresolved (not counted, not ruled out) |
| S05 | Yes | No | Unresolved (not counted, not ruled out) |
| S06 | Yes | No | Unresolved (not counted, not ruled out) |
| S07 | Yes | No | Unresolved (not counted, not ruled out) |
| S08 | Yes | No | Unresolved (not counted, not ruled out) |
| S09 | Yes | No | Unresolved (not counted, not ruled out) |
| S10 | Yes | No | Unresolved (not counted, not ruled out) |
| Total | 10 initially counted | 3 with a record | 3 supported, 7 unresolved |
The counting rule
- Rank commerce software suppliers by distinct supported shops, highest first. Ties break by supplier name, A to Z.
- The analyst first credited Arc for every shop showing the shared checkout. That was the analyst’s mistake: the checkout identifies a payments provider, not a commerce supplier.
- A shop stays supported only when a separate record names the supplier for that shop. A shop without one is unresolved: not counted, and not ruled out.
- The other suppliers’ counts are stipulated in this exercise.
Verification and field worksheet
Check one supplier for yourself.
| Ask | Record |
|---|---|
| Who made the disclosure? | Publisher, dated source and precise passage. |
| What exactly is supplied? | Name the service and the parties in their stated roles. |
| Is the evidence independent? | Trace copies to the first disclosure. Record the separate source, if one exists. |
| What happens if it is withdrawn? | Recheck each affected shop. Preserve surviving evidence. Reorder the complete shortlist. |
Reproduce the retail result
In the public teaching kit, run python verify.py from the extracted folder. It reads retail-input.json, calculates both rankings and compares them with expected-output.json. Python 3 is sufficient.
Expected output (expected-output.json)
{
"before": [
"Arc",
"Birch",
"Cove"
],
"after": [
"Birch",
"Cove",
"Dune"
],
"arc_supported": 3,
"arc_unresolved": 7
}Downloads
- Acquiry-Labs-Supplier-Evidence.pdfThe field note, four pages72.2 KBSHA-256 fa8083b33b6a7e88…
- retail-input.jsonThe fixture: ten shops and the other suppliers’ stipulated counts1.2 KBSHA-256 6fb037cf96f1e956…
- expected-output.jsonExpected output of the example156 BSHA-256 31757aeb61fc65cc…
- verify.pyRecomputes both rankings and checks them against the expected output968 BSHA-256 c8808625fab74a0e…
- shortlist.svgThe editable shortlist diagram1.4 KBSHA-256 94827804b043b488…
- acquiry-labs-retail-teaching-kit-1.0.zipFixture, expected output and verify.py in one folder1.3 KBSHA-256 81fcb67e2c9457a9…
- SHA256SUMS.txtChecksums for every file above535 BSHA-256 f53cc7cb07d65bcc…
Checksum list (SHA256SUMS.txt)
fa8083b33b6a7e88118d9b20f1334282ce8d0a4843978bb56e8eb5e0ed848667 Acquiry-Labs-Supplier-Evidence.pdf
81fcb67e2c9457a9c90d5f6204387fef3041ddd623bf793b312382036ac260e0 acquiry-labs-retail-teaching-kit-1.0.zip
31757aeb61fc65cc30b15f49d55bd5318e1aadb6bbc7ad6256abe69a0fe7db87 expected-output.json
6fb037cf96f1e956ac323f5ec5190c261a8a7e968197e659ee0fce7f8f1fcb86 retail-input.json
94827804b043b488cf4c8d6310e4968ede4882a4927c354d88cb1b7800a58e15 shortlist.svg
c8808625fab74a0e38c6000ecfc8c82e0e4d18c5a968f89a68f712100f3793d6 verify.pyInterpret the result
The demonstration tests a counting decision on supplied evidence. Establishing which company actually supplies a particular merchant takes dated, role-specific research. This example measures neither real lead conversion nor real supplier market share.
Cite this research
One citation covers the field note and its companion dataset. The canonical page address is the stable reference.
Acquiry Labs. Who actually supplies this brand? Research lead Joash Boyton. Research edition 1.0, 13 November 2026. Companion dataset: Embedded Payments Provider Map for Software Platforms, edition 1.1. https://www.acquiry.com/labs/who-supplies-this-brand/editions/1.0/
Edition status
- Research edition
- 1.0, published 13 November 2026
- Credit
- Joash Boyton, Research Lead, Acquiry Labs
- Companion dataset
- Embedded Payments Provider Map for Software Platforms, edition 1.1, evidence checked 13 November 2026
- Canonical address
- https://www.acquiry.com/labs/who-supplies-this-brand/editions/1.0/
- Scope
- Synthetic retail teaching case: the ten shops and four suppliers are fictional and describe no real company. The Squarespace section reports what one public source says.
- Links last checked
13 November 2026, signed out, each returned a page.
- Stripe Squarespace case study: https://stripe.com/customers/squarespace
- Dataset row squarespace-stripe: https://www.acquiry.com/data/embedded-payments-provider-map/#squarespace-stripe/
- Dataset edition 1.1: https://www.acquiry.com/data/embedded-payments-provider-map/editions/1.1/
- Changelog
- 13 November 2026. Research edition 1.0. Field note, fixture, expected output, reproduction script and checksums published, with a live example driven by the fixture. An earlier same-day version of this page used different fictional names and its download files were withdrawn.
Related: What a payments integration tells an acquisition buyer and the embedded payments provider map.