One stock ledger
Storefront, POS, buylist, and marketplace listings all draw from the same inventory record. When a card sells in one place, the available quantity is reduced everywhere else instead of waiting for staff to remember a manual update.
CardNexus
CardNexus integration
Storefront Pro connects CardNexus through its Public API. Exact catalogue mappings drive price and quantity reconciliation, listing updates, and sales import while your storefront, POS, and connected marketplaces continue to use one central stock workflow.
Technical spec
CardNexus sync — how it works
The concrete details of the Storefront Pro ↔ CardNexus integration. No hand-waving — read it before you start, not after.
- Connection
- CardNexus Public API — your API key
- Current scope
- Catalogue mapping, inventory, listings, and sales
- Catalogue
- Cards and sealed products across CardNexus-supported games
- Automation
- Background reconciliation with authoritative sales polling
Capabilities
What the integration does
Concrete features, not marketing bullets.
- Exact catalogue mapping for supported cards and sealed products
- Price and quantity reconciliation with non-destructive listing updates
- CardNexus sales import into the unified fulfilment workflow
- Optional shipment-status updates after separate enablement
- Quarantine and exception visibility before automatic sync is enabled
Operations
How CardNexus fits into one inventory source
Marketplace sync is only useful if staff can trust the numbers at the counter. Storefront Pro treats each channel as an output of the same stock ledger, not as a separate spreadsheet to reconcile later.
Channel-specific rules
Your own storefront can hold margin while marketplace listings compete more aggressively. Pricing rules can reflect fees, shipping expectations, condition, language, and how quickly you want a particular catalogue to move.
Order reconciliation
Orders from external channels are pulled into the same fulfilment queue as online and in-store sales. Staff pick, pack, refund, and report from one place instead of switching between seller portals.
Exception handling
API limits, rejected listings, missing SKUs, and price-rule conflicts are visible in the admin dashboard. The integration is designed to make failures obvious, because silent sync failures are how oversells happen.
Limitations
What it doesn't do
We'd rather tell you the limits before you start than have you discover them after onboarding.
- Requires an active CardNexus seller account and a Public API key with the required account, inventory, listing, and sales scopes
- Automatic sync requires an exact catalogue mapping; ambiguous or conflicting identities are quarantined for review
- CardNexus webhooks currently accelerate sync, while fully paginated sales polling remains authoritative
- Shipment updates are optional and enabled separately
FAQ
Frequently asked questions
- Do I need CardNexus API credentials?
- Yes. CardNexus's Public API uses an API key from your CardNexus account. We connect and validate it during onboarding.
- What does the CardNexus connector sync?
- For exactly mapped catalogue items, it reconciles prices and quantities, maintains listings, imports sales into the fulfilment workflow, and can optionally send shipment updates after that write path is enabled.
- Is CardNexus available with Storefront Pro and Enterprise?
- Yes. CardNexus is available as a supported marketplace channel during onboarding for both full-platform plans.
Storefront Pro
CardNexus sync — included with onboarding
Every marketplace connector is bundled on both full-platform plans. Storefront Pro is £1,000 setup + 2% only on TCG item sales. Enterprise is £25,000/year, billed annually, or £2,499/month when paid monthly, with 0% sales fees, dedicated support, and direct founder access.
Tell us about your store and integrations and we'll help you choose the right package. Pricing is billed in GBP; approximate equivalents move with exchange rates: £1,000 setup is about US$1,337, CA$1,896, or €1,172.