Connecting inventory, pricing, and sales for a collectibles retailer
Octacer helped a trading card and sports memorabilia retailer connect its card-processing app, online storefront, and in-store systems to NetSuite. We fixed workflows that could leave prices out of sync, rebuilt product and supplier feeds, and moved core automations to a self-hosted n8n environment.
- NetSuite
- n8n
- Cardex
- Shopify
- BigCommerce
- Clover
How the data moves 6 steps
-
Cardex item update
A card is processed or reprocessed
-
n8n workflow
Looks up the master SKU in NetSuite
-
NetSuite item master
Item created, updated, or reactivated
-
Upper Deck and Fanatics feeds
Normalized in n8n, then written to NetSuite
-
Shelf-label pricing
Price file exported hourly from NetSuite data
-
Storefronts and POS
Shopify, BigCommerce, and Clover
Validation and workflow cadence from the project record. Not sales or ROI figures.
Validation
20 supplier products checked
Initial production batch: 10 Upper Deck and 10 Fanatics products pushed to NetSuite and checked
Workflow cadence
15-minute Cardex inventory sync
Scheduled from self-hosted n8n. Cardex sales sync nightly and the shelf-label price file exports hourly.
The first figure is a validation batch and the second is a workflow schedule. Neither is a catalog total or a business outcome.
The challenge
Prices, labels, and supplier data all had to agree with NetSuite
A trading card could be processed again after a price change or repurchase. The automation had to identify its existing NetSuite record, decide whether to update or reactivate it, and carry the new price through. In one incident, the printed label showed the new price while NetSuite retained the old one. In another, repeated Shopify events could print two labels for the same price.
The retailer had a separate catalog problem. Upper Deck and Fanatics supplied different product, image, and availability data, but both feeds had to create usable NetSuite records and keep prices and stock current. At the same time, cloud task-runner interruptions were affecting workflows that processed thousands of items.
- Industry
- Trading cards and sports memorabilia
- Project type
- Automation and systems integration
- Octacer's role
- Integration, troubleshooting, workflow migration, and ongoing engineering
- Core systems
- NetSuite, n8n, Cardex, BigCommerce, Shopify, Clover, and Pricefy
- Delivery
- Core workflows live. Supplier imports validated in production batches.
How it works
Two workflows in detail
Steps 1 to 3 follow a reprocessed trading card from Cardex into NetSuite. Steps 4 to 6 follow the Upper Deck and Fanatics supplier feeds. The other delivered work is listed under Delivered scope below.
-
Cardex
Card-processing app that sends item updates
-
n8n
Runs the card, supplier, restocking, and pricing workflows
-
NetSuite
Item master for item records, prices, and stock
-
Step 1: Card processing: find the existing record
CardexWhen Cardex sends an item, the workflow looks up its NetSuite record by master SKU, including inactive records.
-
Step 2: Card processing: create, update, or reactivate
NetSuiteA new SKU creates an item. An active match updates the existing item. An inactive match reactivates the item and adjusts inventory. If more than one record matches, the workflow reports the conflict for review.
-
Step 3: Card processing: carry the new price through
NetSuiteThat lookup matters because a card's title and price can change while the underlying item stays the same. After fixing the missing sell-price mapping, Octacer monitored a real card through the update path and verified that the new price reached NetSuite.
-
Step 4: Supplier feeds: normalize different stock data
n8nFanatics reports a stock quantity. Upper Deck reports whether an item is available. The integration preserves Fanatics quantities and represents Upper Deck availability as one or zero.
-
Step 5: Supplier feeds: confirm each NetSuite write
NetSuiteThe workflow records whether NetSuite accepted a price or stock update before marking the change as synced. A rejected write remains visible for follow-up.
-
Step 6: Supplier feeds: validate in batches
n8nOctacer used separate sandbox and production workflows and tracking tables to validate the import in batches. The initial production batch covered ten products from each supplier. Later production checks verified the revised item setup and inventory rules on one item per supplier.
Prices or stock drifting between your systems?
What we delivered
Delivered scope
Trading card processing
Connected Cardex and NetSuite for item creation, updates, reactivation, inventory adjustments, and label print requests. Fixed the active-item update so a reprocessed card carries its new sell price into NetSuite.
Sales and inventory feeds
Put the NetSuite-to-Cardex sales and inventory feeds live with backfills, scheduled runs, and error alerts. Synced Clover POS cash sales into Shopify and BigCommerce order and inventory records.
Supplier catalog integration
Built n8n workflows to normalize Upper Deck and Fanatics data, create and enrich NetSuite records, and track stock and price changes. Validated production batches and refined source-specific rules for pricing, inventory, categories, and images.
Restocking and pricing
Repaired the Pricefy integration after an API response change caused the restocker to skip products. Migrated scheduled restocking, stock removal, manual stock controls, and the Wrike approval workflow to self-hosted n8n.
Store pricing and customer support
Moved the hourly electronic shelf-label price export to self-hosted n8n. Connected BigCommerce contact submissions and AfterShip delivery events to support workflows in Zendesk.
Workflow operations
Set up self-hosted n8n on Google Cloud with backup, restore, and monitoring tools. Replaced CData calls in active workflows with direct NetSuite calls and added alerts around critical steps.
Evidence from the project record
What we verified
| Evidence type | Verified behavior |
|---|---|
| Live workflow verification | A reprocessed trading card carried its updated sell price into the existing NetSuite item. |
| Production batch verification | Ten Upper Deck and ten Fanatics products were pushed to NetSuite and checked. Image availability varied with what the supplier supplied. |
| Migration comparison | Restocking results matched between cloud and self-hosted runs for SKU quantity, status, and price, apart from stock that changed between runs. |
| Live schedule verification | Cardex inventory synced every 15 minutes, Cardex sales synced nightly, and the shelf-label price file exported hourly from self-hosted n8n. |
Need to fix an integration your store already relies on?
If pricing, inventory, or supplier data drifts between your storefront, POS, and ERP, Octacer can trace where it breaks and rebuild the workflow around how your team operates.
Frequently asked questions
Can n8n connect Cardex to NetSuite?
Yes. In this project, n8n connected Cardex and NetSuite for item creation, updates, reactivation, inventory adjustments, and label print requests. The NetSuite-to-Cardex sales and inventory feeds run on a schedule with backfills and error alerts.
How does the integration handle a trading card that is processed again?
It looks up the NetSuite record by master SKU, including inactive records. A new SKU creates an item, an active match updates the existing item, and an inactive match reactivates the item and adjusts inventory. If more than one record matches, the workflow reports the conflict for review.
How were the Upper Deck and Fanatics feeds handled differently?
Fanatics reports a stock quantity and Upper Deck reports whether an item is available. The integration keeps Fanatics quantities and represents Upper Deck availability as one or zero. It also records whether NetSuite accepted each price or stock update before marking the change as synced.
How was the supplier import validated?
Octacer used separate sandbox and production workflows with tracking tables and validated the import in batches. The initial production batch covered ten products from each supplier. Later production checks verified the revised item setup and inventory rules on one item per supplier.
How often do the Cardex feeds run?
In the live schedule check, Cardex inventory synced every 15 minutes and Cardex sales synced nightly. The electronic shelf-label price file exported hourly from self-hosted n8n.
What moved to self-hosted n8n?
Octacer set up self-hosted n8n on Google Cloud with backup, restore, and monitoring tools, then migrated scheduled restocking, stock removal, manual stock controls, the Wrike approval workflow, and the hourly shelf-label price export. Restocking results matched between cloud and self-hosted runs for SKU quantity, status, and price, apart from stock that changed between runs.