Feed orders into the system
Advice on how to use our API to feed orders into the System. You may want to hand them over from external systems for processing in a common way in the backend office.
Understanding our System
PCG systems are primarily build to support regular deliveries based on subscriptions and assortments, that are assembled on a weekly basis for the fruits and vegetables that are currently available. In addition, packaged food is supported too.
The Backend may be connected to several front end stores (POS), with possibly individual settings (Domains, navigation, customers base or offering).
Orders are generally editable until a last order time.
Alle orders are for specific delivery days: one may choose an automatic next date during logon or set a date automatically or set it while submitting the order. Not that the valid days are provided as part of the Logon Response
MCP service
The API endpoints described below have counterparts in our publicly available MCP Service with OAuth. Check esst.bio for more Details.
This API may be more suitable for interactive AI clients.
API
see the API Intro to understand how to use the API.
The following methods are of interest for this use case:
- api/logon to log on with user credentials.
- api/settour allows to set a delivery date. Choose from the ShopDates
- api/neworder to feed an order
- api/changeorder for changing an open existing order
- api/cancelorder to cancel an open order
- api/logout controlled logout (recommended)
A one-off order for a guest customer may also be created, use the following method:
related
You may manage Subscriptions as part of orders.
To update a remote system based on events on the PCG System, you may use webhooks. They can be set up in the Admin Area of the system, or now also via the API — see setup_webhooks.md.