Catalog & SKU Feed Ingestion
Merchant onboarding means loading thousands of SKUs without corrupting the item master. Representative architecture: the supplier-feed staging and NetSuite item sync we delivered for a multi-channel retailer, adapted for 3PL merchant onboarding. Writing into a WMS item master (such as Extensiv) is not included.
- Logistics/3PL
- n8n
- NetSuite
- Google Sheets
- Catalog Ingestion
- Merchant Onboarding
Overview
The project at a glance
Onboarding a merchant means loading thousands of SKUs from someone else's spreadsheet or feed, and one bad import can corrupt the item master. This representative architecture adapts catalog ingestion we delivered for a multi-channel retailer's supplier feeds: stage and profile before ERP writes, then sync on a backfill / daily / hourly cadence with exception alerts. In that build the item master was NetSuite.
It has not yet been deployed for a 3PL. Writing into a WMS item master (Extensiv, ShipHero and similar) would be new work.
What the engagement had to achieve
- Stage and profile incoming catalogs before anything hits the item master
- Avoid all-or-nothing opaque imports that leave half a catalog written
- Support ongoing sync after go-live (backfill, daily, hourly)
- Make failed batches loud via exception alerts
The story
Every merchant catalog arrives in a different shape
What was at risk
The Challenge
Every new merchant arrives with a catalog in a different shape: a CSV export, a supplier feed, a spreadsheet with merged cells, or a PDF. Before the first inbound receipt, the 3PL needs clean SKUs, descriptions, barcodes, dimensions and weights in its item master. Bulk imports are all-or-nothing and opaque. A malformed row halfway through stops the job — or worse, writes half a catalog. Bad dimensions and weights then break slotting, cartonization and shipping costs downstream.
Malformed rows stall the job or write partial catalogs with no clean resume.
Missing weights and dimensions break slotting, cartonization and shipping cost later.
In the original build the item master was NetSuite. Writing into Extensiv, ShipHero or another WMS item master would be scoped per project.
How we responded
The Solution
The incoming feed lands in a staging area and is profiled (row counts, missing fields, duplicates) before anything is written to the system of record.
After go-live: full backfill, daily reconciliation, hourly deltas — with exception alerts on failed runs (shared pattern with our multi-channel sync page).
Where catalogues are large, ingest in controlled batches rather than one monolithic import. Pause / resume / retry tooling is available as an option; it was not part of the retailer build.
WMS item imports (Extensiv and peers), PIMs and GS1 barcode data are typical targets. PIM integration and barcode validation were not built.
What we built
The concrete capabilities designed, built, and shipped in this engagement.
Stage-and-profile before ERP writes
Incoming supplier / merchant feeds land in Google Sheets staging and are profiled (row counts, missing fields, duplicates) before anything is written to the item master.
Controlled batch ingestion
Catalog ingested in batches rather than one monolithic import — supporting pause / resume / retry tooling pattern.
Pause / resume / retry for operators
An operator can pause a run, fix the source and resume from the last good batch; failed batches retry without re-importing successful ones. (optional; not part of the retailer build)
Three-cadence ongoing sync after go-live
Full backfill, daily reconciliation, and hourly deltas — same reliability layer as our multi-channel order and inventory sync page.
NetSuite item writes from staged feeds
Staged, profiled rows write to NetSuite as the item master (item/inventory integration — not NetSuite WMS).
Step-level exception alerts on failed batches
Failed or stuck batches raise step-level alerts in the ops channel (shared pattern with the multi-channel sync page).
The stack
The tools behind the build, and the role each one played.
n8n
NetSuite
Google Sheets
Slack
What changed
Representative architecture: there are no 3PL results to report yet. The design guarantees below come from the original retailer build.
Beyond the launch
Lasting improvements
The changes that keep paying off after the engagement ended.
- Stage-and-profile-first — bad rows never reach the item master unchecked
- Controlled batches with pause / resume / retry so operators can fix source data mid-run
- Three-cadence sync (backfill / daily / hourly) after go-live
Swipe to see more
All case studies
Want an outcome like this one?
A short introductory call covers what's holding you up, whether we can help, and the first thing worth building.