Invoicing for cooperatives and food businesses: purchases, batches and B2B sales

A cooperative or food business needs two trails that connect without being confused: the commercial trail, from purchase to customer invoice, and the food-safety trail, which identifies the origin and route of a product or batch. A structured invoice proves a sale; by itself it does not replace the traceability required for food operations. The sound method links suppliers, references, quantities, dates and related documents while keeping the production or batch register in a dedicated system when the invoicing application does not manage it.

1. Two records for the same goods

The commercial file answers ‘who ordered, received and paid for what?’ The food-safety file answers ‘where did this item come from, which production used it and which customer received this batch?’ Law 28-07 defines traceability as the capacity to retrace a product through the food chain. Our guide to mandatory invoice fields covers the first record; your ONSSA procedures and competent quality lead govern the second.

Element	Commercial trail	Food-safety or quality trail
Supplier	Record, purchase document, reference and amount	Origin, approval when applicable and received batch
Product	Invoice label, unit, price and tax	Exact name, pack, batch, dates and relevant conditions
Receipt	Received quantity and purchase cost	Checks, inbound batch, acceptance and internal destination
Processing	Cost and sale item	Link from inputs to production and outbound batch under the procedure
Customer	Order, delivery, invoice and payment	Recipient and quantity of each batch when a recall requires it

Do not force everything into a description field. Use a stable reference and keep the batch register separate but reconcilable. If a B2B customer disputes a delivery, the invoice number should lead to the delivery note and then the batch record without searching through WhatsApp messages.

---

2. Cooperative identity and invoice fields

Article 12 of Law 112-12 requires documents sent to third parties, including invoices, to show legibly the cooperative’s name together with the word ‘cooperative’, its registered office, and the place and number of its registration in the cooperatives register. Add the tax details that apply to the entity’s actual position and have the model checked by its accountant.

• Legal heading: Exact registered name, cooperative capacity, office and register details, followed by applicable tax identifiers and contacts. Do not substitute a member’s personal identity.
• Business customer: Legal name, address and ICE or relevant identifier. One clean record prevents twenty spellings for the same reseller.
• Lines: Clear description, quantity, unit, price, discount and tax. For food, bottle, case or kilogram removes ambiguity that the total cannot reveal.
• Delivery: Date, location, quantity actually handed over, reservations and signature or equivalent evidence. Invoice what was delivered under the agreement, not merely what was planned.
• Payment: Due date, method, references and balance. A bank transfer that is not allocated must not leave the invoice looking unpaid.

For a retail sale, also review the required receipt details. When a hotel, shop or distributor needs an invoice, enrich the existing sale with the customer identity instead of retyping the goods.

3. Recommended flow from purchase to payment

This does not require an industrial ERP. It requires one document and one accountable person whenever responsibility changes hands.

1. Create the supplier once and file relevant compliance evidence outside the basic commercial record.
2. Raise or record the purchase document with references, units, expected prices and due date.
3. At receipt, check what arrived. Record batches, dates and food-safety checks separately under the approved procedure.
4. Create sale products with stable names and units; do not use one generic ‘cooperative product’ line for ten items.
5. Confirm the B2B customer’s order, price, pack, address and timing before preparation.
6. Issue a delivery note for the quantity that actually left, with a reference that leads back to the dedicated batch register.
7. Invoice the agreed deliveries, checking identity, tax, discounts, due date and total, then allocate every payment.
8. Archive the commercial file for the applicable period; Article 211 of the 2026 Tax Code notably requires ten years for the invoice copies and accounting records it covers.

Example	Quantity	Commercial reference	Traceability bridge
Olive oil 50 cl	120 bottles	HUILE-50CL	Delivery BL-0087 points to batches L2408-A and L2408-B
Amlou 200 g	48 jars	AMLOU-200	Delivery BL-0087 points to A2608 in the external batch register
Delivery charge	1	LIVRAISON	No batch; the service is shown separately

Typing L2408-A into a note may help a person, but a reliable recall depends on the register that identifies the inputs and quantities, the checks performed and the customers that received the batch. The POS must not be presented as a replacement for that register.

4. How BelloPOS handles the commercial work

With BelloPOS Go, a cooperative can record suppliers and purchases, receive quantities into stock, track cost, sell, issue an invoice from the sale, track customer credit and export invoices. That covers the simple producer-to-outlet flow and removes a second stock entry.

With BelloPOS Pro, the Documents hub adds quotations, sales orders, delivery notes, invoices and credit notes, converting them without retyping the customer, lines or totals. The accounting bridge adds journals and accountant exports. Pro fits resellers that order in advance, receive partially or pay later.

The plan does not change the food-safety limitation: neither Go nor Pro promises food-batch traceability. Keep the dedicated register and use a shared reference on the delivery note or preparation file to reconcile the two trails. Compare the exact scope on the BelloPOS pricing page.

5. Check before sending a B2B invoice

Have the order preparer perform this short check, followed by the person authorised to issue the invoice.

Check	Question	Evidence
Entity	Is the heading the cooperative’s?	Approved model and current register record
Customer	Do the ICE and address belong to the recipient?	Customer record and order
Quantity	Does the invoice match what was delivered?	Signed delivery note or equivalent
Product	Are unit and pack explicit?	Invoice lines and preparation record
Batch	Can the batches be found outside the POS?	Traceability register bridged to the delivery note
Payment	Are deposit, due date and balance consistent?	Allocated payment

Mistakes to avoid

• Using a member’s name instead of the cooperative’s registered identity.
• Confusing a stock-keeping reference with a food-safety batch number.
• Invoicing the original order without adjusting to actual delivery.
• Mixing kilograms, cases and units without stating the pack.
• Overwriting an issued invoice instead of preserving the correction and reason.
• Claiming food traceability because stock falls when a sale is made.
• Leaving purchase and quality records scattered across staff phones.
• Failing to allocate credit notes and payments to the reseller’s balance.

---

Frequently asked questions

Is an invoice enough to trace a food batch?

No. It proves a sale and may carry a useful reference, but traceability must retrace the product’s path. Use a register or system that genuinely links inbound batches, production, dispatches and recipients for the operation.

Which details are specific to a cooperative?

Law 112-12 notably requires the name with the word cooperative, registered office, and the place and number in the cooperatives register. Add the tax details applicable to the cooperative’s validated position.

Can a batch be written in the product description?

Yes as a human pointer, but it does not control quantity by batch, production genealogy, expiry or recalls. It therefore does not turn BelloPOS into a batch system.

Does a professional reseller need an invoice?

Provide a complete invoice suited to the transaction and the business customer’s identity. A delivery note proves handover but does not automatically replace the invoice.

Which BelloPOS plan fits a small cooperative?

Go may cover purchasing, stock, sales, invoicing and credit. Pro is relevant for quotations, orders, deliveries, credit notes and accounting exports. No plan replaces food-batch traceability.

Does BelloPOS calculate the cost of a manufactured recipe?

It tracks purchase prices and stock, but this guide does not claim that it calculates a production bill of materials or the complete cost of a processed batch. Test that requirement separately.

What to take away

Good food-business invoicing is not about placing every fact on one invoice. It is about reconciling separate records: purchase, receipt and quality upstream; order, delivery, invoice and payment downstream. Give the records a shared reference, keep batch traceability in the system designed for it and use the POS to eliminate commercial re-entry. The customer receives a clear invoice, the team has usable stock and the cooperative retains a trail that can be checked if a product must be located.

Sources

The figures and rules quoted above come from these pages, read on the date given in the article.

• Law 112-12 on cooperatives, ODCO, especially article 12
• Law 28-07 on food-product safety, ONSSA
• 2026 General Tax Code, especially articles 145 and 211, read 29 August 2026
• BelloPOS purchasing, suppliers and cost prices, read 29 August 2026
• BelloPOS quotations, orders, deliveries, invoices and credit notes, read 29 August 2026
• BelloPOS prices and plan boundaries, read 29 August 2026

Read next

Other practical guides on the same subject:

• Invoicing for wholesalers and distributors: from purchase order to payment
• Retail-shop invoicing: a receipt at checkout, an invoice for a business customer
• Stock management step by step: a guide for small shops
• Mandatory invoice fields in Morocco: the complete list