AWRA OpsHub Search

The Quote Lines That Are Not Rows

A requisition has line rows. A request for quotation has line rows. A purchase order has line rows. A supplier's quotation has a JSON blob. It is the one document in the chain whose detail is not queryable, and it is the one you most need to compare.

Procurement Insights AWRA OpsHub Team 11 min read

Competitive buying is a line-by-line activity. Three suppliers quote against the same basket, and the useful question is never which total is lowest — it is which supplier is cheapest on which line, and whether the cheapest total is cheapest because it left something out.

Our system answers the first half on screen — an item-by-item comparison across the quotes on a request, with each line awarded to the supplier you choose. The rest of the question is harder, and the reason is structural rather than a missing screen.

One document out of four

Walk the chain and look at how each document stores its detail.

Document How its lines are stored Queryable?
Requisition Rows in their own table, with an item and a quantity Yes
Request for quotation Rows in their own table, linked to items Yes
Supplier quotation A single structured field on the header No
Purchase order Rows in their own table, with quantities and prices Yes

The odd one out is the supplier's document. Everything you asked for is in rows; everything they answered is in a blob.

You can query what you asked for and what you ordered. You cannot query what you were offered.

What that makes hard

Not display — the lines render perfectly well on the quotation itself, and the comparison page reads them out of each quote on a request to lay them side by side, one row per item and supplier, so a line can be awarded to the supplier who quoted it best. What the blob makes hard is anything that requires the database to look across quotations beyond one request.

  • Detecting an omitted line. The most common reason one quote is cheapest is that it quoted for less. A total-versus-total comparison cannot see it, and neither can anybody in a hurry.
  • Price history per item per supplier. What did this supplier quote for this item last time? The information is in the system and cannot be asked for.
  • Any report over quoted prices. Average quoted price by item, by supplier, by quarter — all of it needs rows.

And it explains something we have published elsewhere: the weighted quote score is computed on the header total, with weights across price, delivery time and a rating, even though the line comparison sits on the same page. The total is the one figure the database holds as a column.

The failure mode a blob has and a table does not

This is the part worth carrying to any evaluation, because it generalises well past this product.

A table has a schema. Ask it for a column that does not exist and something errors, immediately and loudly. A structured blob has no schema. Ask it for a key that is not there and you get nothing back — silently, successfully, forever.

That is not hypothetical here. Our receipt-matching service used to read quotation-derived invoice lines by a key the stored data never contained. Every lookup missed. Every line reported as unbilled. The service returned a discrepancy on every order, always, from the day it was written — and nobody found out, because nothing rendered its output and nothing errored.

A missing column would have been found in an afternoon. A missing key was found years later.

Why a Pakistani buyer notices first

Because the buying culture here is genuinely competitive at the line. Multiple quotes are routine rather than exceptional, suppliers are numerous, and the negotiation happens item by item — a buyer who accepts a total without going through the schedule is not doing the job.

That work happens on the request’s comparison page: every quote’s lines side by side, and each line awarded to the supplier chosen for it. What the buyer still assembles by hand is memory — what this supplier quoted for this item last quarter — because that question crosses requests, and the lines are not rows.

It is also the reason the habits below are not tricks. They are what good buyers already do.

Working with it today

  • Quote against a request, always. The request has real line rows, so it is the shared reference every supplier is answering. Without it, three quotes are three unrelated documents.
  • Award on the line comparison, not the total. The item-wise table on the request is the schedule; choose a supplier per line and the orders follow the lines that were won.
  • Check for omitted lines before you look at totals. Count the lines on each quote against the request. This takes ten seconds and it is the one check the comparison leaves to you.
  • Keep your own price memory. Until quoted prices are reportable across requests, note what each supplier quoted for your key items when you award, so next quarter’s comparison has a reference.

The quotation-detail ledger, precisely

What AWRA OpsHub does today

  • Requisitions, requests for quotation and purchase orders all with relational line items linked to catalogue items.
  • Supplier quotations holding their own line detail, displayed on the quotation and carried through to the resulting purchase order's lines.
  • A currency, a tax treatment and a financial snapshot on each quotation, so an agreed price cannot drift.
  • A weighted comparison across quotations on the header total, with a persisted ranking.
  • A supplier portal in which vendors submit and edit their own quotations.
  • A line-by-line comparison across the quotes on a request, one row per item and supplier.
  • Split awards from that comparison, each line awarded to its own supplier, with the price read from the stored quote rather than the form.

More we can add to your workspace

  • Relational quotation line items. The lines are held as a structured field on the header, with no table and no model. Commission it
  • Detection of an omitted or substituted line on a quote. Commission it
  • Price history per item per supplier, or any report over quoted prices. Commission it

Where we point you to a specialist

  • The lines are all there — displayed, and turned into the purchase order's relational lines when an order is raised. What the build adds is querying across quotations, rather than anything about the document itself.
  • The receipt-matching incident described above is fixed. It is quoted here because it is the clearest evidence of how a schemaless field fails, not as a current defect.
  • This is market-neutral. It is what a blob cannot do; this is a market where line-level competitive buying is the norm rather than the exception.

More we can add for you

What we can build for your market on top of the standard product

Everything listed above as something we can add describes what ships in the standard product today — it is a starting point for your market, not a limit on what AWRA OpsHub can do there. Kenya's eTIMS integration and its maintained payroll engine are in the product because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a tax authority pipeline, a bank or mobile money feed, a statutory return format, a rule specific to how your operation runs, or a link to a system you already have is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.

Tax authority pipelines and reporting

Electronic invoicing or invoice registration against your authority's published interface, with retries, a failure queue and a daily report of sales that carry no reference. The regimes across this region differ enough that this is one build per country rather than one build for the region, and the local bench is deep in most of them — so the honest question is usually whether you need this from us at all, or whether you need the operations layer that feeds whatever you already file with.

Local payment rails and bank feeds

Real-time payment collection matched to the invoice, bulk payment files in your bank's format, and statement feeds wired into the Payments Register.

The operational work, which is what most commissions actually are

An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.

Payroll and statutory returns

Statutory payroll and social security schedules computed on live records and produced in the layout each filing body expects. Per-state and per-province variation is the norm rather than the exception here, and it is what makes this a country build rather than a regional one.

Systems you already run

The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.

How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.

Tell us what you need integrated

Our position

Use the request for quotation as your shared basket, compare and award line by line on its comparison page, and count the lines before you read the totals. And if line-level sourcing analysis across requests — price history, quoted prices by quarter — is central to how you buy rather than occasional, raise it as a requirement, because it is a schema change rather than a report.

Three questions that expose this in any system

Show me three quotes side by side, one row per item.

A good answer sounds like

A comparison grid, on screen.

What it actually means

This is the demonstration to ask for, and it is not the same as showing three quotations in a list. Ours is on the request’s quotes page.

What did this supplier quote for this item last year?

A good answer sounds like

A price history.

What it actually means

Requires line-level storage. If it cannot be answered, the data is being kept and not indexed.

Can I award line one to A and line two to B?

A good answer sounds like

Yes, from the comparison.

What it actually means

Split awards are the clearest test of line-level identity, and they are how a competent buyer actually buys.

Make quoted prices reportable

The comparison and the split award are on screen today. If price history per supplier and per item is how you buy, we will scope the line table and the reports against your own request format.

Scope quoted-price reporting

Frequently asked questions

Do the quotation lines reach the purchase order?

Yes. When an order is raised from a quotation, the lines become relational purchase-order line items with quantities and prices. So the detail is not lost — it becomes queryable at the moment it becomes an order. Before that, the comparison on a request reads the quote lines directly.

Could a report be written over the quotation lines anyway?

In principle a structured field can be read, and in practice it is fragile in a specific way: nothing enforces that every quotation stores the same keys, so a report over it is correct until the day it silently is not. That is precisely how the receipt-matching defect survived for years.

Is this a big change to fix?

It is a schema change with a data migration behind it — a table, a model, and a conversion of existing quotations — plus everything downstream that reads the current shape. That makes it a project rather than a feature, and worth scoping properly against how you actually buy rather than assumed.

Share this article

LinkedIn X WhatsApp

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center