ERP integrations overview
Summary
Many merchants connect an ERP or warehouse system to B2B Plus so data can flow automatically: inventory spreadsheets uploaded by integration jobs, purchase orders created from the ERP, orders or splits exported for fulfillment updates, and fulfillment status sent back when shipments complete.
Day-to-day credential management and monitoring are usually owned by operations/IT alongside your Shopify Partner.
Business purpose
- Remove manual double-entry between Shopify B2B and back-office systems.
- Keep inventory records and order splits aligned with how finance and warehouses actually operate.
- Provide measurable export reliability (often visible on the Dashboard or Logs).
Step-by-step usage (operations)
Align on scope
- Confirm which objects integrate: inventory CSV, purchase orders, orders/splits export, fulfillment status updates.
- Identify systems of record—for example whether available quantity is authoritative in the ERP or edited in both places.
Coordinate uploads
- Schedule ERP extracts to match CSV templates your partner validated.
- After automated uploads, review Logs or dashboard upload summaries for failures.
- Download failed records, fix at source, and re-submit.
Validate splits with finance/warehouse
- After enabling or changing split rules in Settings, process a pilot order end-to-end through the ERP.
- Confirm each split ID maps to the correct warehouse or channel in the ERP.
Monitor fulfillment callbacks
When integrations push fulfillment status back:
- Spot-check a shipped order in Shopify versus ERP same day.
- If mismatched, capture order ID, split ID (if any), and timestamps for your integration team.
Important notes
- API authentication details belong in technical runbooks—merchants focus on business outcomes and exception queues.
- Rate limits and retries may delay spikes—avoid stacking multiple full uploads at the same minute without coordination.
Limitations
- Not every Shopify feature has an ERP twin—document manual bridges (gift lines, custom adjustments).
- Historical corrections may require both systems updated—Logs show app-side attempts but not ERP edits.
FAQs
Who creates API keys?
Typically your developer or IT admin using the app’s credential workflow—never share secrets in email or tickets.
Can we pause integrations during inventory counts?
Yes—coordinate freeze windows; pause schedules on the ERP side or temporarily disable jobs per your runbook.
Troubleshooting
| Symptom | Suggested action |
|---|---|
| Upload succeeds but rows missing | Check failed-record CSV; validate SKU existence and warehouses. |
| ERP shows wrong fulfillment state | Verify PATCH/update calls in Logs; confirm split versus non-split endpoints match order structure. |
| Duplicate POs | Align ERP idempotency keys and timestamps; search Logs for duplicate create calls. |