Forbinde

Merchant guide

Wix → Picqer

Reference only — complete Guided Onboarding for this pair. Same EU Picqer destination for every cart: API URL + key, auto shipment webhook, productcode match, paid unfulfilled order.

Operators: the live checklist lives in Guided Onboarding. This page is the setup reference — credentials, SKUs, labels vs warehouse, troubleshooting, and limits.

Open Picqer

Provider requirements

Picqer is an EU warehouse WMS (pick/pack). Guided Onboarding is the live checklist; this is what to paste.

Wix store
Install Forbinde from the Wix App Market. After authorize, continue in Forbinde (app.forbinde.com) — Destinations and Connections, not a Wix iframe. Tracking writes back through Forbinde fulfillments.
Create a Picqer API key
In Picqer: Settings → API keys → New API key. Name it Forbinde and copy the key immediately (shown once). The API URL is https://YOUR-SUBDOMAIN.picqer.com/api/v1 — the same subdomain you use to log in.
Paste credentials in Forbinde Destinations
Destinations → Add production → Picqer. Paste the API URL and API key. Password / API secret is not used. Save, then Test connection.
Shipment webhook is automatic
After Save, Forbinde registers picklists.shipments.created and stores the HMAC secret. Destinations should show Shipment webhook: Connected. If Missing or Inactive, use Repair / re-register. Do not create that hook by hand in Picqer.

SKU and catalog

Picqer is the only destination that requires SKUs
Each paid line must exist in Picqer as productcode. Identical store SKU and productcode auto-match. Map in Catalog only when they differ. Create missing products in Picqer before the first live order.
Refresh catalog after SKU changes
If you change a store SKU or Picqer productcode, run Catalog sync before the next warehouse order. Matching is exact — leading zeros and letter case count.

Labels-only vs WMS

Warehouse fulfillment turns on automatically
Pairing a store to Picqer is pick/pack, not the LumaSwift labels path. Do not fulfill or buy a label in the store. Forbinde creates a Picqer order; Picqer picks, packs, and ships.
After a paid order
Store marks it paid. Forbinde sends the order to Picqer. When Picqer creates a shipment, tracking writes back through the auto-registered webhook.

Troubleshooting

Authentication expired
Create a new Picqer API key, paste it on Destinations, Test connection, then Repair webhook.
Held — product not found
The store SKU is not a Picqer productcode. Create the product in Picqer or map the SKU in Catalog, then retry.
Shipped in Picqer, no tracking on the store
Destinations → Picqer should show Shipment webhook: Connected. If Missing or Inactive, Repair / re-register. Then check Events for writeback errors.

Known limitations

No store fulfill
If you fulfill in the store, Picqer never sees the order and tracking cannot write back.
Create-order only after send
Forbinde can send new orders. Store changes after send stay in Warehouse still open until you handle them in Picqer.

Need help? Support · Operator sign-in