Inventory and Fulfillment Sync
Keep stock levels accurate across Shopify, NetSuite, and 3PL warehouses feeding files over SFTP or EDI, with reorder triggers before you sell out.
The problem
Stock counts drift between the storefront, the ERP, and warehouse systems that report on their own schedules and in their own formats. Overselling triggers cancellations and refunds, while stale buffers leave sellable inventory hidden. 3PL feeds arrive as files that someone has to fetch, parse, and key in.
How it runs on Neblex
Neblex keeps inventory aligned from every direction. Poll-based change detection watches NetSuite item availability with cursors and content hashing, Shopify reports sales and cancellations over webhooks, and 3PL warehouses feed files over SFTP or EDI documents, X12 or EDIFACT over AS2, on their own schedule.
Each change passes through field mapping and transforms into a single stock position per SKU and location, held in Data Tables and pushed back out channel by channel. Chunked batch processing with checkpoints lets large nightly files resume cleanly after an interruption, and cron schedules run full reconciliation sweeps that catch drift the incremental updates miss.
Reorder rules read thresholds from Data Tables and raise NetSuite purchase orders before a SKU sells out, with an optional approval step for large buys. When a feed arrives malformed or a warehouse misses its window, the flow opens an inbox task instead of silently keeping stale counts.
Step by step
Watch every source
Webhooks capture Shopify sales, poll-based change detection tracks NetSuite availability, and SFTP or EDI feeds bring in 3PL counts.
Normalize the formats
Field mapping and transforms convert each source, including X12 and EDIFACT documents, into one stock schema.
Update the stock position
Data Tables hold the current position per SKU and location, updated as each change lands.
Push levels to channels
Updated levels sync to Shopify and NetSuite with chunked batch processing, checkpointed so large updates resume after failure.
Trigger reorders early
When a SKU crosses its Data Tables threshold, the flow raises a NetSuite purchase order, with approval for large amounts.
Reconcile on schedule
A cron-scheduled sweep compares all sources and flags discrepancies to the inbox rather than papering over them.
Platform capabilities used
- Poll-based change detection
- EDI X12 and EDIFACT over AS2
- SFTP file exchange
- Chunked batch processing with checkpoints
- Data Tables for stock state
- Cron schedules
Common questions
Does Neblex support 3PL partners that only exchange EDI?
Yes. Neblex handles X12 and EDIFACT documents with AS2 transport, alongside plain file exchange over SFTP and FTP. Inbound documents map into the same stock schema as API sources through field mapping and transforms.
What happens when a nightly file fails halfway?
Chunked batch processing writes checkpoints as it goes, so a failed run resumes from the last checkpoint instead of starting over. You can also replay from the exact step that broke.
Can reorders require sign-off?
Yes. An approval step can pause the run for purchase orders above a threshold you keep in Data Tables. The approver acts from the task inbox, and SLA timers escalate if the request sits.
Related use cases
Order Orchestration
Sync new Shopify orders across NetSuite and ShipEngine with parallel steps, compensation on failure, and exceptions flagged before customers notice.
EcommerceReturns and Refund Processing
Validate return requests against policy, issue Stripe refunds automatically for clean cases, and route edge cases to a reviewer before money moves.
Want this running on your stack?
Neblex Integration Fabric is in beta: full platform, free while in beta. Bring this workflow and we will map it to your systems.