For products sold individually, enter the number of individual items being billed and a unit price for one of those items. If nine replacement handles were supplied at 7.50 each, quantity nine and price 7.50 express that basis directly. Confirm the delivery and pricing records before relying on the resulting line amount.
Quantity is one part of the line-item preparation workflow. The main risk is often a mismatch between what is counted and what the price represents. A field can contain a valid positive number while still charging for packs as though they were individual products, or for an entire order that was only partly delivered.
Identify the unit being counted
Read the order’s unit wording and the agreed price together. “Each”, “box” and “set” are different counting bases. Ten boxes containing four products are not the same as ten individual products. Decide which basis the invoice should express, then make both the quantity and unit price follow it.
For a fictional order of three boxes at 24.00 per box, entering quantity three and unit box preserves the quoted basis. Entering twelve individual units requires a properly agreed or derived price of 6.00 per item. Changing only the quantity would multiply the charge incorrectly.
A readable unit label helps the recipient understand the basis, but it performs no conversion. The creator treats the quantity and price as entered numbers. If the source price is per hundred items or another base quantity, resolve that basis before entry; the current app has no separate price-base quantity field.
Count the quantity being invoiced
Compare the order with the fulfilment evidence. If a customer ordered twenty units but this invoice bills a delivery of twelve, use the quantity appropriate to that invoice. Do not copy the order total simply because it appears prominently on the purchase order.
Check whether earlier invoices already cover some of the supply. A delivery record alone may not reveal duplicate billing. Keep the order, fulfilment record and earlier billing references together in your preparation process so the new invoice can be reviewed against the remaining quantity.
The creator does not connect to inventory, delivery records or previous invoices. It cannot identify a repeated shipment or confirm that an item was actually supplied. Its validation checks the supported data format and required fields, not the completeness of your fulfilment history.
Use separate lines for distinct products
Different models, sizes or agreed prices should remain distinguishable. Combining five handles of one model and four of another into nine generic handles can conceal a wrong price or make the customer’s goods-receipt comparison difficult. Separate rows usually make those differences easier to inspect.
Items with identical commercial details may be grouped if that matches the transaction and recipient requirements. Before grouping, check that the price, unit, description and tax treatment are truly the same. Similar-looking goods are not necessarily interchangeable for billing purposes.
A stock code can help identify variants in your source records. The guide to product codes and descriptions explains why a visible code and a dedicated structured item identifier serve different purposes. The current creator does not implement separate seller-item or buyer-item identifier fields.
Check positive and fractional values
For individually counted goods, a whole number is often the expected quantity. If you find a fractional value such as 2.5, investigate whether the product is actually sold by length, weight, a partial pack or another measurable basis. Do not round it to three merely to make the row look conventional.
The app accepts positive quantities with up to four decimal places, but that input capability does not establish that a fractional quantity is commercially appropriate. Conversely, it does not make an indivisible product divisible. Use the agreement and delivery evidence to determine the correct basis.
Do not use a negative quantity to record returned goods in the current creator. It supports ordinary positive invoices, not a credit-note workflow. If the transaction requires a correction or credit, use an appropriate process that preserves the relationship to the original invoice and required document semantics.
Review quantity changes before export
After correcting a quantity, inspect the resulting line amount and document totals. A change may also alter the rounded percentage discount and tax. The live preview recalculates the values, but it cannot tell you whether the new quantity agrees with the delivery record.
Read the description again if it contains a written count. Remove or update contradictory prose. Then check the remaining rows for duplicates, especially if you added a replacement line instead of editing the original. An invoice can have individually valid rows that accidentally bill the same supply twice.
Keep the reviewed delivery basis with the final invoice record. Export only after the quantity, price basis and scope have been checked together. A clean preview is useful evidence of what you prepared, while the supporting business records explain why those particular quantities were billed and how the recipient can reconcile them.
For a high-volume order, review the count by delivery batch before combining it. A simple preparation record showing batch quantities and the resulting billed count can expose a missing carton or a duplicated receipt without adding unnecessary detail to the customer-facing description.