Dropshipping Operations Flow — BAKES × Indmar

Exported from 01_dropshipping_flowchart.svg · Inventory sync + order-to-fulfillment

Download SVG
Dropshipping Operations Flow — BAKES × Indmar Sales channel: BAKES Shopify store · Integration middleware: HexaSync · ERP: Acumatica · Shipping: ShipStation · Supplier inventory: Indmar via FTP · Shopify location: SNOQ A. Inventory Synchronization (continuous / scheduled) INDMAR Supplier / Vendor Owns physical inventory Pushes stock file periodically FTP SERVER Inventory Drop Zone Receives stock / qty files Source of truth for available qty HEXASYNC Integration Middleware Pulls stock from FTP Maps SKU → Shopify location BAKES SHOPIFY Sales Channel Warehouse / Location: SNOQ Online available quantity updated SNOQ LOCATION Shopify Warehouse Virtual stock from Indmar Used at checkout / ATP 1. Push stock file 2. Pull / poll FTP 3. Sync inventory 4. Update qty Note: HexaSync maps Indmar SKUs to Shopify products and writes available quantity into the SNOQ location so storefront ATP (Available-to-Promise) reflects supplier stock without BAKES holding goods. B. Order-to-Fulfillment Flow (event-driven after checkout) CUSTOMER Buyer Places order on storefront Pays via Shopify checkout BAKES SHOPIFY Order Created Sales order + line items Allocated against SNOQ HEXASYNC Order Integration Detects new Shopify order Transforms & pushes to ERP ACUMATICA Cloud ERP Sales Order created Financials + fulfillment control SHIPSTATION Shipping Execution Label, carrier, tracking Shipment confirmation SHOPIFY Order Fulfilled Tracking + notify buyer Status = Fulfilled 5. Checkout 6. New order 7. Push SO 8. Send to ship 9. Tracking / shipment update → Acumatica 10. Fulfillment data 11. HexaSync writes fulfillment + tracking number back to Shopify C. Step-by-step sequence (as specified) 1 Indmar → FTP Indmar pushes inventory / stock file to a dedicated FTP folder. 2 HexaSync ← FTP HexaSync polls or pulls stock from Indmar FTP on a schedule. 3 HexaSync → Shopify SNOQ Stock is written to warehouse location SNOQ on BAKES store. 4 Customer order on Shopify Buyer checks out; order is created against SNOQ available quantity. 5 Shopify → HexaSync → Acumatica New order is ingested by HexaSync and posted as a Sales Order in ERP. 6 Acumatica → ShipStation Order is sent to ShipStation for label generation and shipment. 7 ShipStation → Acumatica Tracking / shipped status is written back to the Sales Order / Shipment. 8 HexaSync fulfills Shopify HexaSync posts fulfillment + tracking to Shopify; customer is notified. System roles & data contracts • BAKES — Merchant. Sells on Shopify. Does not hold the physical goods (dropship model). • Indmar — Supplier. Source of inventory. Pushes stock snapshots/deltas to FTP. • FTP — File-based inventory interface between Indmar and HexaSync (CSV / XML / JSON file drop). • HexaSync — iPaaS middleware (Beehexa). Owns mapping, polling, transformation, error handling, and bidirectional sync. • SNOQ — Shopify Location / warehouse on the BAKES store that represents Indmar-available stock for ATP and order allocation. • Acumatica — System of record for sales orders, customers, financials, and shipment documents after the Shopify order is captured. • ShipStation — Shipping execution layer. Receives the order from Acumatica, produces carrier labels / tracking, and posts shipment confirmation back. • Closed loop — Shopify (sell) → HexaSync → Acumatica (record) → ShipStation (ship) → Acumatica (confirm) → HexaSync → Shopify (fulfill & notify). • Typical dropship implication — Physical pick/pack may be performed by Indmar or a 3PL; ShipStation is the software control plane that feeds tracking back into the ERP/storefront loop.