2026-06-unstable schema is an early preview and may still receive breaking changes before the first stable version.The Pickware ERP GraphQL API gives integrations the same data and operations Pickware uses itself. Feed ERP data into reporting tools, push purchase orders from a procurement tool, or hand off picks to a custom fulfillment layer.
Start with the operational areas merchants often need to connect: stock handling, purchasing, goods receipts, warehouse organization, fulfillment, product lookup, and quotes — and react to changes as they happen.
Read stock levels, set stock quantities, apply stock deltas, and transfer stock between bin locations.
ShopifyShopware 6Create supplier orders, manage line items, and update order or payment states for merchant-specific workflows.
ShopifyShopware 6Record goods receipts into a warehouse and connect them to the supplier orders they deliver.
ShopifyShopware 6Manage product-supplier assignments, purchase prices, delivery times, and order constraints.
ShopifyShopware 6List warehouses and bin locations, create new warehouses, and maintain storage-location codes.
ShopifyShopware 6Read orders and trigger complete shipment workflows from a selected or default warehouse.
ShopifyShopware 6Look up products and variants by product number, GTIN, and exposed identifiers used by integrations.
ShopifyShopware 6Read sales quotes and their line items, open a new quote for a customer, and price its positions.
ShopifyShopware 6Subscribe to webhook topics such as a completely shipped order, and reconcile with a query when a notification was missed.
ShopifyShopware 6Four properties matter once an integration is wired into the merchant’s daily ERP operations.
Subscribe to webhooks instead of polling: integrations react the moment something changes and spend no requests on unchanged data.
Cursor pagination and filters make it practical to build recurring imports, exports, and background jobs.
Queries and mutations document the read or write scopes a token needs before an integration calls them.
The typed schema, explicit field selection, and per-field access scopes give LLM-driven agents a much narrower surface to reason about than a sprawling REST API.