Keep a quantity attached to its unit before calculating an amount

A fictional buyer asks for 12 cartons, each containing 24 items. Another requests 12 individual items. Treating both as the number 12 loses the information needed to prepare a dependable offer.

Preserve the original request

Store and display quantity and unit together. Product specialists approve valid sales units and any conversion rules. For this fictional carton example, 12 multiplied by 24 is 288 items; that arithmetic is not a universal pack size or a recommendation for a real product.

Do not infer units from an image, translated label or current catalogue default. A past quotation may concern an earlier packaging arrangement. The record needs enough context to explain what was requested and what was quoted.

Separate amounts and commercial decisions

Where a project includes pricing or payment, currency and amount must remain paired. A displayed number or browser return page does not establish a settled payment or accepted order. The provider-supported evidence and approved business rules determine the next action.

This site's RFQ planner does not calculate a price or process a payment. A development project involving financial actions needs its own confirmed interface, review and test arrangement.

Review a correction

Change the requested unit after the first enquiry. Ask staff to identify the original and revised values and explain which offer now applies. Test a missing unit and a rejected input without losing the rest of the request.

See order integrations and RFQ development for the surrounding workflow.

Worked example: a pack size changes after a quotation

The fictional item K-17 is sold in cartons of 24 when a buyer requests 12 cartons. The enquiry therefore describes 12 cartons and, under the reviewed example rule, 288 individual items. Staff issue quotation Q-72 against that requirement.

Later, the current catalogue changes to cartons of 20. Recalculating the historical request using today's default would turn the same entered number into 240 items. The buyer did not change the request; the application changed the meaning by looking up a newer packaging rule.

The record needs the original quantity, unit and relevant packaging context. The business decides which information forms the quotation snapshot and how an actual correction is approved. The current catalogue remains useful for new requests, but it should not silently rewrite the basis of an issued offer.

Compare a request and a correction

Create a new fictional enquiry after the pack change. Twelve current cartons now describe 240 items under the new example rule. That does not make Q-72 wrong; the records concern different packaging contexts. A staff view should explain both without forcing the operator to remember when the catalogue changed.

Now let the original buyer explicitly amend their requirement to 240 individual items. Record the correction and identify which quotation needs review. The adjustment is a new business event, not an unexplained replacement of the original quantity. Product and commercial owners decide the permitted treatment.

Review the receiving system

Transfer both records into a suitable isolated fixture. Check the original quantity/unit pair, any approved conversion and the applicable quotation reference. A destination expecting individual items needs an explicit mapping; it must not interpret every incoming number as its own default unit.

Include an unknown unit and a missing packaging context. The transfer should request review instead of using whichever catalogue value is convenient. These invented counts demonstrate arithmetic and record identity only. They are not real pack sizes, prices, supply commitments or a universal conversion rule.