For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

How the Shopify app connects your store to pyck

Audience: Logistics Manager

The pyck Shopify app links a Shopify store to your warehouse. It copies your shop data into pyck so the warehouse knows what to pick, and it lets pyck report back what it shipped and what is on the shelf.

The two directions

Everything the app does falls into one of two directions.

Direction
What travels
When

Shopify to pyck

Products, customers and orders

Whenever the record changes in Shopify, and on demand for the whole catalogue

pyck to Shopify

Shipped orders with tracking, and stock counts

Whenever the warehouse finishes a pick or records a stock movement

Shopify stays the shop. pyck stays the warehouse. Neither replaces the other.

Shopify to pyck

When you create or change a product, a customer or an order, Shopify tells the app and the app writes it into pyck. Products arrive as items your pickers can find, orders arrive as picking orders. A product variant with no SKU is never sent, because pyck identifies stock by SKU.

An update changes only the fields that come from Shopify. Fields your warehouse maintains in pyck stay as they are. See What a sync overwrites in pyck.

You can also send everything at once. The Activity page has a Full sync button that walks your whole catalogue, which is how you bring an existing store over on day one.

pyck to Shopify

When the warehouse has picked and packed an order, pyck calls the app and the app marks the order fulfilled in Shopify, with the tracking number if there is one. The customer gets their shipping email from Shopify as usual.

pyck can also drive your stock counts. See Warehouse stock for how that works and what it overwrites.

What a connection is

A connection is one pyck tenant your store syncs to. You set up your first one during setup, and it is called production — your real warehouse.

A store can have several connections at once. That is how you run a test or staging tenant alongside the live one: it receives a copy of your data so you can try things against real records, but it never ships an order and never changes your stock. Only one connection can be the production connection, and only that one is allowed to fulfil orders and write stock back.

Each connection has a short label — production, stage, eu-prod — and that label is how you steer individual products, customers and orders at one tenant rather than all of them. See Sending data to several pyck tenants.

Where to go next

Last updated

Was this helpful?