Logiwa Help for Shopify: IO Connection, Warehouse Mapping and Sync

Logiwa promises onboarding in days. These are the settings that decide whether those days go smoothly.

Mapping locations to buildings. Each Shopify location maps to one Logiwa warehouse. Several locations can share a warehouse, but one location can't split across two, so stock held in several buildings needs a location plan in Shopify first.

Available or On Hand. Logiwa can push either figure. On Hand is meant for stores where Shopify is the only sales channel. Selling on marketplaces as well means pushing Available.

Catalog repair. A product without a SKU fails with "SKU cannot be empty", and kit or bundle lines without SKUs stop orders downloading. Fixing this is often the first billable task.

Download filters. Payment statuses and order tags decide what reaches the floor. Set them so unpaid, test or hold-for-review orders stay out.

Legacy-to-public switch. Older connections still run, but new setups go through the public app. Moving over means rechecking every option against how the old connection behaved.

Stock accuracy across channels. Logiwa routes orders across warehouses and channels. Keeping Shopify, marketplaces and the floor in agreement is work for inventory management specialists.

Single-warehouse stores. One building, tidy SKUs and only Shopify as a channel: Logiwa's onboarding may be all you need.

Logiwa's connector has specific one-way behaviors. Candidates who have run it will name them without prompting.

"What happens when I edit a product?" The right answer: after creation, product changes don't sync in either direction and deletions don't carry over. Expect them to propose a routine for new SKUs and price changes.

"How are cancellations handled?" A Shopify cancellation cancels the Logiwa order for good, while a cancellation made in Logiwa never reaches Shopify. Good candidates write a support rule for each direction.

"Can my team fix addresses in Logiwa?" Editing an order by hand in Logiwa breaks shipment info sync. Someone who knows this suggests another route for address changes.

Gaps that should worry you. Assuming that switching on inventory sync pushes existing stock, never mentioning "Track quantity" in Shopify, or ignoring the client field on a 3PL account.

A small paid review. A written audit of your connection settings plus ten test orders, one partial shipment and one cancellation among them. For links to other back-office systems, ERP and backend integrators fit better.

Direction. Products and orders flow from Shopify to Logiwa. Inventory and shipment details flow back. Product downloads run daily; the other jobs run on a schedule or from the Run button.

Which orders download. Only unfulfilled ones. Drafts, fulfilled, archived and canceled orders stay behind, and the open-order import reaches back two months at most.

Partial shipments. Shipment info can mark an order Fulfilled or Partially Fulfilled. Creating partial orders is possible only with product downloads off, and it can't be combined with creating missing products.

Event-driven stock. Inventory moves when something changes in Logiwa. Turning the setting on may not push existing stock, new channel orders don't trigger a sync, and a product that stops tracking quantity in Shopify stops syncing.

3PL accounts. The connection's client must match the client that owns the SKUs, or orders don't sync.

Data and language. The app reads customers, products, locations and the last 60 days of orders. The listing is English only.

A Logiwa engagement breaks into these jobs. Many stores need only two or three.