{
"event": "replenishmentCreated",
"occurred_at": "2026-10-12T09:00:00-06:00",
"store_id": 1234,
"replenishment_id": 55010,
"status": "REQUESTED",
"sell_ahead": false,
"appointment_date": null,
"products": [
{
"product_code": "7501234567890",
"skus": [
"SKU-RED-M"
],
"expected_quantity": 200,
"received_quantity": 0
}
],
"supplier_invoices": [],
"sequence": 1791234567890
}Replenishment announced
Cubbo sends this event to your replenishment webhook URL when a replenishment (inbound receipt)
is created before any merchandise has arrived, i.e. created in status WITHOUT_SCHEDULING,
PENDING, REQUESTED or IN_TRANSIT. Receipts that are born already in the warehouse (reverse
logistics, relocations, transfers) do not produce this event; they only produce
replenishmentStatus events on later transitions.
- This feed must be enabled for your integration (opt-in, with its own URL). It does not require the order webhook feed.
productslists the expected and received quantities per product;received_quantityis 0 at this point.sequenceis the timestamp of the transition in epoch milliseconds; order events of the same replenishment by it.X-Cubbo-Idempotency-Keyis deterministic (replenishment:<id>:<status>:<integration>), so a retry carries the same key.
{
"event": "replenishmentCreated",
"occurred_at": "2026-10-12T09:00:00-06:00",
"store_id": 1234,
"replenishment_id": 55010,
"status": "REQUESTED",
"sell_ahead": false,
"appointment_date": null,
"products": [
{
"product_code": "7501234567890",
"skus": [
"SKU-RED-M"
],
"expected_quantity": 200,
"received_quantity": 0
}
],
"supplier_invoices": [],
"sequence": 1791234567890
}Authorizations
Headers
Name of the event (orderUpdated, orderFulfilled, shippingUpdated, inventoryMovement,
replenishmentStatus, replenishmentCreated, replenishmentScheduled). Route on this header,
not on the URL: all feeds can share one endpoint. Treat a request without this header as an order
event.
orderUpdated, orderFulfilled, shippingUpdated, inventoryMovement, replenishmentStatus, replenishmentCreated, replenishmentScheduled Body
Payload of the replenishmentCreated event.
Response
Acknowledge receipt with any 2xx status. The response body is ignored. A 429 or any 5xx response is retried; any other 4xx response is treated as a permanent rejection and is not retried. Replenishment events for one integration are delivered one at a time, in order.