Past the
published bands.
Catalogues bigger than the largest tier, procurement that needs paperwork, and the same contract everyone else gets.
Beyond 2,000
The published tiers stop at the largest band. Past it, enrichment volume and scan cadence are set against your catalogue rather than a table.
Yours
Procurement, security review, invoicing and data-handling terms — handled as paperwork rather than as an exception to a self-serve flow.
A named contact
A technical contact who knows your catalogue, rather than a queue position.
What does not change
The write contract is not negotiable in either direction. Enterprise stores get the same dedicated metafield namespace, the same allowlist refusing every other mutation, and the same byte-for-byte revert — we do not widen the permissions for a larger account. How the contract is enforced.
Scoring is the same published rubric too, so an internal team can audit our numbers against their own. The methodology.
