Integrations
If your system talks, Planograma connects to it.
Shops, marketplaces and ERPs — the ones below are already running in production. Everything else goes through the Open API, or gets built: we answer every integration request within 48 hours.
- 10+
- platforms live in production
- 48h
- answer on a new integration request
- Any
- system with an API can connect
Already live · eCommerce & marketplace
Every store you already sell in.
Orders land in Planograma as they are placed. Stock levels travel back to every channel, so a product sold in one shop stops being available in the others.
Orders, stock and fulfilment status, two-way.
Orders, stock and fulfilment status, two-way.
Orders, stock and fulfilment status, two-way.
Orders, stock and fulfilment status, two-way.
Multi-marketplace listings and orders in one feed.
Orders, stock and fulfilment status, two-way.
Already live · ERP & business systems
The warehouse and the back office, on the same numbers.
Products, partners and documents move between Planograma and your ERP, so receipts, issues and stock corrections don't get typed twice.
Documents and stock in sync.
Documents and stock in sync.
Documents and stock in sync.
Shipping documents and AWB flow.
Open API
Anything the app can do, your system can do.
A REST API over JSON with token authentication, available on every plan. Build the integration we don't have yet, or push warehouse data straight into the tools your team already lives in.
API access comes with your Planograma account. The full, current reference lives in the Planograma manual.
Example endpoints
Examples of what the API covers — the exact paths are in the manual.
- GET POST/v1/products
- GET/v1/stocks
- GET POST/v1/orders
- GET POST/v1/purchase-orders
- GET/v1/locations
- GET POST/v1/shipments
Webhooks
- order.fulfilled
- stock.changed
- shipment.created
Integration request
The list above is a snapshot, not a limit.
Most of what runs today started as a customer asking for it. Couriers, accounting software, in-house systems, a spreadsheet a supplier insists on — if there's an endpoint, a file drop or a database on the other side, there's a way in.
- An answer within 48 hours — yes, no, or what it takes
- A developer looks at it, not a sales sequence
- Sandbox credentials on request
Prefer email? Write to us directly