Independent IFS Cloud practice · Supply Chain
The order you shipped for nothing, because the price line was zero
The customer order looked complete. It had a part, a quantity, a delivery date, and it moved through the warehouse like any other. What it did not have was a price, or it carried a zero one, and no step in the flow refused to ship a line worth nothing. The goods left, the delivery confirmed, and the invoice, when it came, billed for exactly what the line said it was worth: nothing. The unit price sits on the order line in IFS Cloud from the moment it is entered, so a line about to ship at zero is a number you can read before the truck leaves, not after the customer has free goods.
Key takeaways
- A missing price is a revenue problem, not a fulfilment one: IFS Cloud holds the price on the order line, but nothing routinely stops a line worth zero from shipping.
- This is not a below-cost order, where a real price is simply too low. Here there is no meaningful price at all.
- It leads straight into delivered but not invoiced territory: an invoice for zero is, in every way that matters, no invoice at all.
- Left alone it ships free goods, distorts margin reporting, and turns into an awkward retrospective invoice a customer never expected.
- Unit price and line value are readable through standard OData, so an unpriced or zero-priced line is knowable before it ships, not after the goods are gone.
Most sales exceptions are felt by the customer: a late order, a short line, a wrong item. A zero-priced line is the quiet one, because from the customer’s side everything is perfect, and better than perfect: they received goods and were billed nothing. Nobody on the outside will point it out. The only party losing is you, and the loss stays invisible until someone reconciles shipped value against invoiced value, or a margin report reads strangely and somebody asks why. Reading order lines for a missing price before they ship is far cheaper than clawing revenue back from a customer weeks later.
1.How does a line ship without a price?
In IFS Cloud a sales order line takes a price, usually from a price list, an agreement, or a manual entry. Normally that price is present and correct before the line is released. The gap opens when the price resolves to zero or nothing: a new part has no price list entry, an agreement expired and nothing replaced it, a manual line was entered in a hurry, or a configuration returned a zero the person entering the order never noticed.
None of these blocks the order. The line has everything the warehouse needs, so it picks, packs, and ships, and the price, or its absence, is nobody’s job at that point. The order moves to invoicing carrying a value of zero, and unless someone reads the price before the goods leave, the first time the gap is visible is on an invoice that asks the customer for nothing.
2.What an unpriced line actually costs
The cost is revenue given away, plus the awkward job of asking a customer to pay for something you already told them was free.
- Free goods — a line billed at zero hands the customer product at no charge, and the money is gone the moment it ships.
- Awkward retro-billing — recovering the revenue means invoicing after the fact for goods the customer received believing they were free, which invites a dispute.
- Distorted margin — a zero-value line drags reported margin and makes a product or customer look far less profitable than it is.
- Control gap — goods leaving with no price is a straightforward finding for anyone reviewing revenue completeness.
A wrong price gets queried by a customer who thinks they were overcharged. A zero price gets queried by no one, because the customer is delighted and you are the only one out of pocket. That is why it lasts until a reconciliation catches it.
Illustrative only: one low-value line shipped at zero is a write-off nobody misses; the same gap recurring on new parts or expired agreements is steady revenue walking out of the door. The threshold that matters is simple: no line worth selling should ship at zero, and that is a rule you can read before dispatch.
3.Seeing the unpriced line in IFS Cloud
The check is already possible with data IFS Cloud exposes. A sales order line carries its unit price and computed value alongside part, quantity, customer, and delivery status. All of it is readable through standard OData projections without writing anything back. Turning that into a watch list is a scheduled read of two things:
- Priced at zero, not yet shipped — any order line with a zero or empty unit price that is still open, so it can be corrected before the goods leave, ranked by quantity and part so the material ones surface first.
- Shipped at zero, not yet invoiced — lines that already left carrying no price, the ones to catch before an invoice for nothing is raised.
This is the same read-and-flag discipline that catches a delivered but not invoiced order: the facts are already in the system, they just need something to read the price on the line and raise the ones that would bill the customer nothing.
4.The manual check versus a systematic one
A sharp order-desk clerk spots a missing price when they happen to look at the line. The problem is that a zero-priced line looks complete: it has a part and a quantity, it does not error, and it flows. Nothing draws the eye to a price field that is simply blank, and habit does not surface a value that is quietly zero.
| Manual order review | Systematic monitor | |
|---|---|---|
| Trigger | Someone happens to notice, or a margin report queries it | Every open line checked for a missing price each day |
| What surfaces | Zero lines found by luck, often after shipment | Every unpriced line before dispatch, ranked by material value |
| After shipment | Easy to miss a zero line already delivered | Shipped-at-zero lines flagged before an invoice is raised |
| Continuity | Depends on who is on the order desk that day | Runs the same regardless of workload or staffing |
| IFS footprint | None, but nothing checks the price before it ships | Read-only; no object added to IFS Cloud |
Because it is a read-only monitoring pattern, it never writes back to IFS Cloud. It surfaces the lines that would ship or bill at zero and leaves the price fix, the pricing decision, or the customer conversation with the person who owns the account.
5.Rolling it out without adding noise
- Start before dispatch — the highest-value list is open lines still correctable, so the price is fixed before the goods leave.
- Dry-run a full period — log what would have been flagged before a single alert reaches the order desk.
- Separate legitimate zeros — free samples and genuine no-charge lines exist, so allow a marked reason and flag only the unexplained ones.
- No upgrade footprint — standard OData reads only, so an R1/R2 release leaves it untouched and nothing new lives inside IFS Cloud.
6.Frequently asked questions
Does IFS Cloud not warn when a line has no price?
It can warn at entry, but a zero price is a valid value, not an error, so the order still releases and ships. The gap is the line that resolved to zero quietly, from an expired agreement or a missing price list entry, and carried on through fulfilment because nothing downstream refuses a value of nothing.
How is this different from a below-cost sales order?
A below-cost order has a real price that is simply too low to cover cost. A missing price has no meaningful price at all: the line bills zero. One is a margin decision to review; the other is revenue that never gets billed unless someone catches the blank before it ships.
What data does IFS Cloud need to expose to flag it?
The unit price and computed value on the sales order line, with its part, quantity, and delivery status, through standard OData projections. Reading those on a schedule is enough to list every open line priced at zero before dispatch, and every shipped line still to be invoiced at zero, ranked by the value at stake.
Does monitoring for unpriced lines write anything back to IFS Cloud?
No. The pattern reads the price on the order line through standard OData and raises alerts outside IFS. Nothing is written back, so there is no upgrade footprint and no new object inside the client’s system.
7.About the author
Dariusz Myśliwiec — 25+ years in ERP and supply chain, 17+ on IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally as an independent practice — you talk to the consultant who builds it.
Selected clients: Betafence (PRÆSIDIAD) · Newag · RADPOL · Fugro · NGK Ceramics · ATLAS.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Never ship a line worth nothing
Tell me where your orders go out carrying a zero price behind them. On a 30-minute fit call I’ll show you how the SCM Automation Pack reads the price on every open line and raises the ones that would bill the customer nothing — with a dry-run period before a single alert reaches the order desk.