Manage a unified product catalog, sync inventory across every channel and warehouse, and configure safety stock buffers.
WarpWare maintains a master product catalog — a single source of truth for every SKU across all your channels. When you connect a platform, WarpWare discovers its products and maps them into the master catalog.
Each platform represents products differently — Shopify has variants with inventory_item_ids, WooCommerce uses variation IDs, Amazon uses ASINs and MSKUs. WarpWare bridges these by linking platform-specific variants to your master SKU.
Tip: If a product on a connected platform doesn't match any existing master SKU, WarpWare creates a new master product automatically. You can merge duplicates later from the Products page.
Inventory sources are automatically discovered from your connected platforms. Each connection that supports inventory becomes a source — no manual configuration needed.
Each inventory source can be configured with one of four sync directions. This controls whether WarpWare reads from it, writes to it, both, or neither.
WarpWare reads inventory levels from this source and uses them to calculate available quantity. The source is read-only.
Example: A 3PL warehouse that reports stock levels. WarpWare pulls their numbers but never writes back.
WarpWare writes calculated inventory levels to this destination. It does not read from it — the destination receives updates only.
Example: A Shopify store that should reflect aggregated inventory from multiple warehouses.
WarpWare both reads from and writes to this connection. Stock adjustments flow in both directions.
Example: A primary warehouse that is both the source of truth and needs to receive adjustments from sales.
Inventory sync is turned off for this source. The connection still functions for orders but inventory data is ignored.
Example: A sales channel where you manage inventory manually or through another tool.
Buffers let you hold back a portion of your inventory as safety stock. WarpWare supports buffers at two levels and combines them into a single formula.
Set a fixed buffer quantity on any master product. This amount is subtracted from the available quantity before syncing to push destinations. Useful for reserving stock for offline sales or wholesale.
Set a buffer on a specific inventory source. This is subtracted from that source's reported quantity before it enters the aggregation. Useful when a warehouse consistently over-reports.
Example:
Warehouse A reports 100 units (source buffer: 5)
Warehouse B reports 50 units (source buffer: 0)
Product buffer: 10
Available = (100 - 5) + (50 - 0) - 10 = 135 units pushed to sales channels
Note: Buffers never cause negative availability. If the calculated result is below zero, WarpWare pushes 0 to the destination.
Each sales channel and warehouse system has its own concept of "locations" — physical warehouses, retail stores, or fulfillment centers. WarpWare maps these locations across platforms so inventory flows to the right place.
When you connect a platform, WarpWare automatically fetches available locations (Shopify locations, Extensiv facilities, Acumatica warehouses). If only one location exists, it's selected automatically.
For platforms with multiple locations, a dropdown is provided in the connection settings. Select which location WarpWare should read from (orders) and write to (inventory). You can change this at any time.
| Platform | Location Concept | Used For |
|---|---|---|
| Shopify | Locations (warehouse, store) | Inventory push, order filtering |
| Extensiv | Facilities | Order routing, inventory source |
| Acumatica | Warehouses (by ID) | Order/shipment filtering |
| Veeqo | Warehouses | Inventory aggregation |
Important: If you change a location mapping after initial setup, inventory levels will be adjusted at the new location on the next push cycle. The old location's levels are not zeroed out automatically — manage that on the platform directly.
Reach out and we'll help you map your sources, configure buffers, and verify sync.