Logiwa streamlines your warehouse management with a user-friendly self-onboarding process for sales channels. This article walks you through the prerequisites, setup, and operational rules for your BigCommerce sales channel.

Before connecting BigCommerce to Logiwa, you must create a dedicated API account in your BigCommerce control panel to generate the secure credentials (Store Hash and API Key) Logiwa needs to communicate with your store.

ℹ️ Note: This setup is a one-time process and must be performed by a user with Store Owner or Admin access to your BigCommerce control panel.

🔒 Credential Security: Treat the API Key as a password. Store it securely and only share it with authorized integration administrators.

Connecting your BigCommerce store to Logiwa is entirely self-service. You'll select and enter everything below directly on the connection screens — there's nothing you need to send to Logiwa in advance beyond the Store Hash and API Key you generated above.

Map your storefront's shipping method names (e.g., "Free Shipping") to the matching Logiwa carrier services, so tracking updates are sent back to BigCommerce correctly.

💡 Post-Activation Configuration: Shipping Method Mapping is set up after your connection is activated, via Manage Configuration in Logiwa — you don't need to have this ready beforehand.

To prevent fulfillment delays and inventory discrepancies, review these operational business rules.

To prevent overselling, Logiwa sends the Available to Sell quantity to BigCommerce, not the total physical On-Hand count. For kit items, Logiwa syncs inventory using the Net Kitting Capacity quantity instead.

💡 Why this matters: This ensures that inventory already reserved for other customers is never listed as available on BigCommerce. You can confirm these numbers yourself in the Logiwa UI by navigating to Reports > Inventory > Available to Promise (ATP).

⚠️ Known Limitation — Kit Components Are Not Received From BigCommerce: BigCommerce does not support defining kit or bundle components, so Logiwa can only pull the kit item itself (the parent SKU) from BigCommerce during Product Synchronization. Component details are not received from BigCommerce and must be configured directly in Logiwa before the kit item can be fulfilled correctly.

For a shipment update to transfer successfully to BigCommerce, the carrier used must already exist in Logiwa as a Carrier or Custom Carrier. If it doesn't, the shipment update will fail (see Error Handling below).

BigCommerce will reject a shipment update for an order that has already been canceled or refunded on the storefront.

ℹ️ Reading these tables: Fields shown in parentheses are technical BigCommerce or Logiwa field names used by the system. The text before the parentheses is the everyday, user-facing label.

Cadence & Trigger: Scheduled automation running every 10 minutes. Logiwa pulls orders with an "Awaiting Fulfillment" status.

Business Rules: Automatically brings new orders from BigCommerce into Logiwa, ready for your warehouse team to pick, pack, and ship — no manual entry required.

Cadence & Trigger: Scheduled automation running every 15 minutes, once an order's status changes to Shipped in Logiwa.

Business Rules: Once an order has shipped from your warehouse, Logiwa automatically sends the shipment details to BigCommerce, updating the order status and providing tracking information to your customer.

⚠️ When Shipment Updates Can Fail: To successfully update a shipment, the request must include a valid Order ID, the line items shipped, and tracking information. Missing or invalid data — or an order that has already been canceled or refunded — will cause the update to fail.

Cadence & Trigger: Scheduled sync running every 10 minutes.

Business Rules: Updates your BigCommerce listings to reflect current stock levels. As described above, the quantity sent is Available to Sell, not total On-Hand (Net Kitting Capacity for kit items).

ℹ️ Note: Inventory tracking must be enabled on the corresponding product in BigCommerce for these updates to be applied.

Cadence & Trigger: Scheduled sync running every 15 minutes.

Business Rules: Retrieves all active products, establishing the SKU master data in Logiwa.

⚠️ Known Limitation — Kit Items: As noted above, kit item components cannot be created by BigCommerce. Product Synchronization pulls only the parent (kit) SKU — component assignment must be configured directly in Logiwa.

Every system event captures the following diagnostic markers (where applicable):

💡 Note on Log Access: Processing logs are not accessible via the Logiwa user interface dashboard, though log details for specific transactions can be shared upon request. All troubleshooting inquiries must be directed to the Support team by opening a ticket through HubSpot.

ℹ️ When opening a support ticket, include: your BigCommerce Store Hash / store name; the time of the error; the BigCommerce Order ID (if applicable); the subject line of the error email; and any error message shown in the email.

⚠️ Testing runs against your live BigCommerce Store: This integration does not use a BigCommerce sandbox environment, so the UAT steps below run against your live store. To avoid leaving test data in your live catalog, use clearly-labeled test customer and product names (e.g., "ZZ-TEST Customer"), and delete or deactivate them once UAT is complete.

Expected Result: Order appears in Logiwa as a shipment order.

Expected Result: BigCommerce order is automatically updated with tracking details.

Expected Result: BigCommerce inventory level reflects the Available to Sell quantity from Logiwa.

Expected Result: Product appears (or updates) in Logiwa.

💡 If any test fails, refer to the Flow-Specific Error Scenarios above. If the issue persists, open a support ticket with the details listed in that section.