Pickware GraphQL API overview

The Pickware GraphQL API is the API of Pickware ERP for Shopify merchants. It helps developers and agencies build custom integrations that read ERP data or run selected ERP workflows. The current 2026-06-unstable schema focuses on stock, purchasing, goods receipts, warehouses, bin locations, orders, quotes, documents, products, and supplier data.

The documentation has two parts:

• Guides explain how to work with the API and describe common merchant integration use cases.
• The API reference is generated from the GraphQL schema and documents the exact queries, mutations, fields, inputs, and required scopes.

What you can build

• Synchronize stock levels across products, warehouses, and bin locations.
• Apply stock corrections and transfer stock between bin locations.
• Create and manage supplier orders and supplier order line items.
• Maintain product-supplier configurations such as purchase prices, supplier product numbers, delivery times, and order constraints.
• Create goods receipts and move them through approval and completion.
• Manage warehouses and bin-location codes.
• Read orders represented in Pickware ERP and trigger complete shipment workflows.
• Find products and variants by product number, GTIN, or other exposed identifiers.
• Read sales quotations with their line items, state, and the order they were converted into, and open a new quote for a customer.
• Get notified over HTTPS when an order ships, a goods receipt is completed, or a product runs out of stock.

Where to go next

• Follow Getting started to run your first query.
• Read Authentication before calling protected operations.
• Open the Product stock use case for the stock workflow.
• Review Working with lists before building synchronization jobs.
• Read Webhooks to react to changes instead of polling for them.
• Read Rate limits before taking an integration into production.
• Use the API reference when you need the exact GraphQL field or input shape.

API version

The current schema is 2026-06-unstable, served at POST /api/graphql/2026-06-unstable and documented in its API reference. Schema versions use date-based slugs, and the -unstable suffix marks this preview as a schema that may still receive breaking changes before the first stable release. Future versions will be published as separate generated references so existing integrations can keep using the version they were built against. See Versioning for details.