Retail purchase management software holds the purchase order as a record with a life: drafted, sent, confirmed by the supplier, expected on a date, received in full or in part, changed, closed or cancelled. It shows what is on order at any moment, what is late, what arrived different from what was ordered, and what the supplier's invoice should be compared against. With Pentoggle, a retailer can describe how buying actually works and generate the starting application around it.
This page is about the order. Deciding what to order and how much is Retail Replenishment Software. Counting the delivery at the door is Retail Goods Receiving Software. The supplier as a relationship, with terms, lead times and performance, is Retail Supplier Management Software. Paying the invoice is Retail Vendor Payment Software. This page is the document that connects them.
Most retailers already run an accounting system such as QuickBooks, Tally or Xero, which records the supplier's invoice when it is entered. That stays where it is. What is often still managed outside it is the order before the invoice exists: what was asked for, at what cost, when it was promised, and whether it came.
Key takeaways
- A purchase order is the store's record of what it agreed to buy. Without it, the supplier's invoice is the only record, and the store is checking the supplier's work against the supplier's own document.
- Open orders are money committed and stock not yet sellable. A store that cannot list its open orders does not know either figure.
- Partial deliveries are normal. An order that arrives in three shipments over two weeks needs a record that holds all three against the one order.
- The order that arrived different from what was ordered is where purchasing problems become cash problems, and the difference is only visible if the order was recorded before the delivery.
- A useful number is open purchase orders past their expected date, by count and by value.
The spreadsheet is often not the problem
A purchase register with the supplier, the date, what was ordered and the total is a working system for a store with a handful of suppliers, and many run one accurately.
The trouble starts at identifiable points.
When the order is an email or a phone call
The order was placed by message or by phone. The supplier's confirmation, if there was one, is in a chat thread. When the delivery arrives, what was ordered is a matter of memory on both sides.
When the order arrives in pieces
Forty units ordered, twenty-five delivered today, the rest promised next week. The register shows the order as delivered, or as not delivered, and neither is true.
When nobody knows what is on order
Two people place orders. A fast-moving item is ordered twice. A slow-moving item is not reordered because someone thinks it is already on order.
When the invoice is the only document
The supplier's invoice arrives and is entered into accounting. Whether it matches what was ordered, at the cost that was agreed, is not checked because the order was never written down in a form that could be checked against.
What retail purchase management software holds
Purchase orders
Supplier, items and variants, quantities, agreed cost per unit, expected delivery date, delivery location and terms.
Order status
Draft, sent, confirmed, partially received, received, closed, cancelled, with the date of each change.
Supplier confirmation
Whether the supplier confirmed, on what date, with any changes to quantity, cost or date.
Receipts against the order
Each delivery recorded against the order, so that ordered, received to date and outstanding are visible per line.
Changes and cancellations
Lines added, removed, requantified or repriced after the order was placed, with who made the change and why.
Open order view
Everything on order right now, by supplier, by expected date, by item, with value.
Late orders
Orders past their expected date with nothing or only part received, and how many days past.
Link to invoice
The supplier's invoice held against the order and its receipts, so that ordered, received and invoiced can be compared before payment.
The order is the store's own record
The reason to write a purchase order is not bureaucracy. It is that without one, the store has no document of its own.
The supplier has an order confirmation, a delivery note and an invoice, all produced by the supplier, all reflecting the supplier's understanding of what was agreed. If the store's only record is those documents, then any check the store does is a check of the supplier's documents against each other, and they will agree, because the same person produced them.
A purchase order written by the store before the delivery is the one document that reflects the store's side of the agreement: the items it asked for, the quantities, the cost it was quoted, the date it was promised. It is the reference that the delivery note is compared against at the door, and that the invoice is compared against before payment.
This does not require suspicion of suppliers. Most differences between order and delivery are ordinary: a substitution, a short shipment, a cost change that was mentioned on the phone and not written down. The purchase order makes those differences visible and gives both sides a shared record to resolve them against. Suppliers who deal with retailers that keep purchase orders often prefer it, because it settles disputes faster.
Open orders are committed money and unsellable stock
A store that cannot produce a list of its open purchase orders is missing two numbers it needs.
The first is money committed. Every confirmed order is an amount the store has agreed to pay. Added up across suppliers, it is the purchasing exposure for the coming weeks, and it is a figure the accounting system does not have because the invoices do not exist yet. A store planning its cash for the month needs it.
The second is stock on the way. Every open order line is quantity that will arrive and become sellable. The replenishment decision for any item depends on it: stock on hand plus stock on order against expected sales. A store that reorders without seeing what is already on order over-orders, and the over-order sits in the back store until it becomes dead stock.
The open order view also surfaces the orders that have gone quiet. An order sent three weeks ago with no confirmation and no delivery is either forgotten by the supplier or forgotten by the store, and neither is visible in a register that only records what was sent.
The order that arrived different
Purchasing problems become cash problems at a specific moment: when the delivery differs from the order and the difference is not recorded.
The common differences are short shipment, where fewer units arrive than were ordered; substitution, where a different variant or a different product arrives in place of the one ordered; over-shipment, where more arrives than was ordered, sometimes at the supplier's initiative; cost variance, where the invoice shows a higher unit cost than the order; and damage in transit, where the units arrived but cannot be sold.
Each has a correct response, and the response depends on the difference being visible. A short shipment means the outstanding quantity stays open on the order and the invoice should be for what arrived. A substitution needs a decision to accept or return. An over-shipment needs a decision to keep and pay or send back. A cost variance needs a conversation before payment. Damage needs a claim.
When the order was recorded before delivery and the receipt is recorded against it, all of these appear as line-level differences that someone can act on. When the order lives in memory, they appear months later as a stock count that does not match, a margin that is lower than expected, or a supplier balance nobody can reconcile.
Comparing ordered, received and invoiced before payment is described on Retail Vendor Payment Software. It depends entirely on the order having been written down first.
Where purchasing looks different by business type
- Grocery Store Software, where orders go out daily to many suppliers and short shipments on fresh items are routine.
- Fashion Retail Software, where orders are placed a season ahead, arrive in drops and are rarely delivered exactly as ordered.
- Electronics Retail Software, where cost changes between order and delivery and the invoice has to be checked line by line.
- Hardware Store Software, where thousands of low-value items are ordered from a small number of distributors on a schedule.
- Multi-Store Retail Software, where orders are placed centrally for delivery to several locations.
- Wholesale Distributor Software, where the purchase order is to a manufacturer and comes with schemes, minimums and a lead time measured in weeks.
Why retailers choose Pentoggle for purchase management
The order as the store's own document
Written before delivery, in the store's system, as the reference for the door and for the invoice.
Partial receipts against one order
Three deliveries against one order held as one record, with ordered, received and outstanding per line.
Open orders as a daily view
What is on order, what it is worth, what is late, on a phone.
Changes with a name and a reason
Lines added, removed or repriced after the order went out, recorded rather than remembered.
Sits around your accounting
QuickBooks, Tally, Xero and comparable systems continue recording the supplier's invoice and the payment. Pentoggle adds the order before the invoice and the comparison against it.
A useful number for purchase management
Open purchase orders past their expected date, by count and by value.
It is the list of promises that have not been kept, and a store that has it can act on it today: a call to the supplier, an alternative source, or a decision to cancel. A store that does not have it finds out when the shelf is empty.
Read it by supplier. Late orders cluster, and a supplier whose orders are regularly past date is a supplier whose lead time in your system is wrong or whose reliability has changed. Either way the finding belongs on Retail Supplier Management Software.
Read the value as well as the count. Ten small late orders and one large one are different problems, and the large one is the one that affects cash planning.
Ready to build retail purchase management software?
You know what you paid your suppliers last month.
You may not be able to say what is on order right now, what it will cost, or which orders are late.
Describe your suppliers, how you place orders and how deliveries arrive to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.
Related resources
- Retail Supplier Management Software →
- Retail Goods Receiving Software →
- Retail Replenishment Software →
- Retail Vendor Payment Software
- Retail Inventory Management Software →
- Wholesale Distributor Software
- AI Software for Retail Businesses →