Fulfiller guide

Build the physical side — stock, locations, pickup and duty context.

Fulfiller guide

You are a Fulfiller if you hold the physical goods: you have locations, you know your stock, and you pick up or ship orders and supply the duty/tax context for a destination.

What you build

The shape of a Fulfiller's data

• Location — a stock-holding point with coordinates, capability flags, and a duty/tax context.
• InventoryItem — a quantity of a variant at a location.
• Duty context — excise + VAT inputs the pricing engine needs for a destination.

Minimal flow

1. POST /v1/locations            → declare a stock location (+ capability, coords)
2. POST /v1/inventory            → declare stock for a variant at a location
3. GET  /v1/inventory/network-snapshot  → node capability + stock + duty context (requires read:network)

Note: GET /v1/inventory/network-snapshot returns the whole-network view and requires the read:network scope, which ordinary partner keys do not receive. Most integrations use the scoped list endpoints instead.

Next steps

• Stock & locations
• Pickup
• Duty context