Purchase orders aligned with what stores actually need
Automated purchasing derived from the replenishment plan, aligned with supplier lead times, delivery cycles, and working capital objectives — executed directly to ERP, EDI, or WMS.
- Inventory reduction
- 25%
- Days of inventory
- -18
- Lost sales reduction
- 33%
From the replenishment plan to the purchase order
The right purchase order is not calculated store by store, nor inherited from what was bought last month. It derives from what the whole network will need within the supplier's delivery horizon, net of what is already in stores and in the warehouse, and adjusted for minimum order quantity, pack multiple, lead time and the working capital available.
Celes consolidates that need per supplier and proposes the purchasing decision with three answers: what, how much and when. The buyer reviews exceptions, not lists; approves or adjusts; and the order goes to the ERP, by EDI or to the supplier portal with no manual entry. Every order is traced back to the demand that justified it, the same number the S&OP process uses and that the supplier can see through CelesLink.
What stores need determines what gets bought
Every purchase order originates from the store-level replenishment plan. The system aggregates the real needs of all stores and consolidates them into supplier-level orders — respecting order cycles, minimum quantities, and lead times. Purchasing is a direct consequence of demand, not a separate decision.
Supplier
Alpina
Cycle
Weekly
Lead time
5 days
The right timing for every order
Celes calculates not just what to buy, but when to buy it. Each order is scheduled based on the supplier calendar, DC capacity, and coverage objectives — balancing product availability against inventory investment.
From calculation to supplier, with no manual steps
Purchase orders are transmitted directly to the retailer's ERP, EDI, or WMS. Supplier → DC → Store or Supplier → Store, depending on the distribution model. No manual entry. No rework.
Consolidated order
Completed
Sent to ERP/EDI
Completed
Supplier → DC → Store
In transit
“With Celes, we moved from reactive decisions to a data-driven planning process that lets us anticipate real demand.”
Celes Autopilot takes this further.
Purchase orders are generated and transmitted autonomously. Leadership defines the financial objectives and supplier priorities. AI operates within those rules.
Learn about Celes AutopilotFrequently asked questions
How does Celes calculate a purchase order?
From what the whole network will need within the supplier's lead time, net of inventory in stores and warehouse, adjusted for minimum order quantity, pack multiples, lead time and working capital. The buyer reviews exceptions and approves; the order goes to the ERP, by EDI or to the supplier portal.
Does Celes replace the purchasing team?
No. Celes prepares the decision (what, how much and when) with the demand that justifies it, and the buyer decides on exceptions, negotiations and suppliers. The time once spent building lists goes into negotiating and handling atypical cases.
Does it account for MOQs, lead times and supplier promotions?
Yes. Minimum order quantity, pack multiple, lead time and its variability are constraints of the calculation, and supplier promotions or price changes can be entered as commercial decisions that adjust the quantity and timing of the order.
How does it integrate with my ERP?
Celes connects to the ERP to read inventory, master data and receipts, and to write the approved order. It supports API, file and EDI integrations, and keeps every order traceable back to the demand that originated it.
How does it relate to CelesLink?
CelesLink shares the retailer's demand plan with the supplier so they plan production and deliveries on the same number. The Celes purchase order is the outcome of that plan; CelesLink lets the supplier see it coming and confirm capacity beforehand.
Want to see it in action?
Talk to our team and we'll show you how it works with your operation.