Logiwa streamlines warehouse operations with a self-service connection for Squarespace Commerce. This article is the complete setup, configuration, and operations guide — written from both a storefront and a warehouse perspective.

This integration is bidirectional. Logiwa downloads paid orders and your physical product catalog from Squarespace, pushes Available-to-Promise inventory (including kits and bundles) back to the storefront, and writes shipment tracking details to Squarespace when an order is fulfilled.

Connecting Squarespace to Logiwa is self-service. You generate an API key in Squarespace, then complete the connection wizard using the embedded setup link provided by the Logiwa Integration Team.

ℹ️ What you need on hand: Administrator access to the Squarespace site and the embedded Logiwa setup link. If the Authenticate tab lists Logiwa, you will also need the Logiwa API user credentials from the Integration Team. Always have the Logiwa client identifier and warehouse identifier for this connection.

⚠️ Squarespace plan requirement: Orders, Inventory, Products, and Transactions API keys are available on Squarespace Commerce Advanced. If Developer API Keys do not offer those scopes, upgrade the site plan before generating a key.

You will paste this key into the Authenticate tab during connection setup. Squarespace shows the secret only once, so copy it before you close the dialog.

🔒 Keep the key somewhere safe: Treat the Squarespace API key like a password. If you lose it, you must generate a new key and reconnect. Do not email the key in plain text.

The connection wizard is an embedded link from the Logiwa Integration Team. It walks through three tabs: Overview, Customize, and Authenticate.

On the Customize tab, fill in the fields for each workflow you enabled, then continue to Authenticate.

💡 Requested shipping option maps in Logiwa workflows: Squarespace sends the shopper's requested shipping option on each order. Bind that field in Logiwa workflows so the warehouse order receives the actual carrier and shipping option your operation uses. If no workflow match exists, the original requested option text is retained.

The Authenticate tab lists only the applications this wizard still needs credentials for. If a Logiwa connection is already in place, the Logiwa tile is omitted — in that case you only need to enter the Squarespace API key.

⚠️ When Logiwa is not listed: If the Authenticate tab does not show a Logiwa connection, skip Logiwa credentials entirely. Paste the Squarespace API key, click Connect to Squarespace, then click Finish.

If Logiwa is listed, connect Logiwa first, then Squarespace. Any application that appears must show Connected before you finish.

ℹ️ Note: After you grant access, the Squarespace API key is stored encrypted in the Logiwa credential vault. You do not need to re-enter it unless you rotate the key or the Squarespace connection is revoked.

💡 Sandbox testing is available: When Logiwa is listed on the Authenticate tab, you can choose Production or Sandbox. Validate the connection in Sandbox when you can, then switch to Production before go-live.

Review these business rules before you turn the schedulers loose on live orders. They prevent duplicate orders, inventory races, and fulfillment writebacks that Squarespace would reject.

For example, if a Squarespace order number is 10024, it will be created in Logiwa as SQU-10024.

The SQU- prefix helps Logiwa identify Squarespace orders and prevents duplicate orders. If the same order is downloaded more than once, Logiwa will recognize SQU-10024 as an existing order and will not create a duplicate shipment order.

Each sync run compares the order's createdOn timestamp with the integration's lastRun cursor:

Squarespace sends the shopper's requested shipping option with each order. Connect that field to Logiwa workflows so the shipment order is assigned the actual carrier and shipping option your warehouse uses (for example, mapping "Express Shipping" to UPS Next Day). Without a matching workflow, the original requested option text is kept on the order.

💡 Why this matters: Set up these workflow mappings before you enable Order Sync, so live orders land on the correct carrier setup instead of requiring a manual change in Logiwa.

A canceled Squarespace order automatically cancels the matching unpicked/unpacked shipment order in Logiwa. If the warehouse has already entered picking or packing, Logiwa rejects the automated cancellation and emails the configured Email Receiver so operations can stop the wave manually.

Product catalog sync ingests PHYSICAL product types only. Digital goods and service items never enter the warehouse item master.

Logiwa does not send an absolute stock figure to Squarespace. It calculates the difference between Logiwa ATP and the current Squarespace quantity, then posts an increment or decrement. Each request includes a unique 10-digit idempotency key so a retried call cannot double-adjust stock.

💡 Why this matters: Relative adjustments protect against race conditions — for example, a shopper buying the last unit on Squarespace while Logiwa is also posting a receiving adjustment. Overwrite logic would clobber the storefront sale; a delta will not.

For kits and bundles, sellable quantity is not stored as its own on-hand balance. Logiwa recalculates parent ATP from component ATP and the quantity required per kit, then pushes that figure to Squarespace.

If several Squarespace orders were merged for warehouse picking, the fulfillment job splits them back to the original SQU- order codes before it calls Squarespace. Each storefront order receives its own tracking payload.

Order download filters on PENDING or CANCELED. FULFILLED orders are skipped so a first-time connection does not flood the warehouse with already-shipped history. The lastRun cursor is initialized at go-live for the same reason.

ℹ️ Reading these tables: The left column is the source system field. The right column is where that value lands in the target system. Logic/notes describe prefixes, fallbacks, and hardcoded rules.

Four scheduled jobs run independently. A failure in one SKU or order does not stop the rest of that batch.

Cadence & trigger: Scheduled automation every 5 minutes, 24/7. Logiwa pulls orders whose fulfillment status is PENDING or whose status is CANCELED.

Business rules: New orders are created, modified orders are updated (see Operational Rules above), and canceled storefront orders cancel matching unpicked shipment orders in Logiwa. The requested shipping option is passed through so Logiwa workflows can assign the actual carrier and shipping option.

Cadence & trigger: Every 15 minutes, or on demand. The first run downloads the full physical catalog; later runs only pull items modified since lastRun.

Business rules: Each variant is processed in two phases — create the product master, then upsert the product listing. Squarespace Variant IDs are stored in Product Listings so inventory adjustments can target the correct storefront variant. A failure on one SKU sends an alert and continues with the next variant.

Cadence & trigger: Every 10 minutes. Source data is Logiwa transaction history (receiving, adjustments, transfers, picking, returns) plus the kit inventory report.

SKUs are de-duplicated and sent in batches of up to 50. Quantity is Available-to-Promise, not raw on-hand:

Cadence & trigger: Every 15 minutes. Selects Logiwa shipment orders in status Shipped or Completed where ShipmentExported = false.

After Squarespace accepts the fulfillment, Logiwa marks the shipping line exported so the same tracking number is not posted again.

Every system event captures the following diagnostic markers where applicable:

💡 Note on log access: Processing logs are not available in the Logiwa user interface. Details for a specific transaction can be shared on request. Open a support ticket through HubSpot for troubleshooting. This integration is also monitored by the Logiwa Integration Team.

ℹ️ When opening a support ticket, include: the Squarespace site/store name; the SQU- order code or SKU involved; the time of the error; the workflow that failed (orders, products, inventory, or fulfillment); and any error message from the notification email.