Wholesale ordering software
The wider platform category for replacing calls, email, WhatsApp and spreadsheets with structured buyer ordering and supplier-side review.
Use this glossary to align sales, operations, finance and buyer onboarding around the same wholesale ordering language. The goal is not to collect buzzwords. It is to define the terms that decide whether a supplier-owned ordering rollout reduces calls, messages, pricing mistakes and invoice cleanup.

Orderlion publishes glossary-style buying education for wholesalers, while Fresho help content explains customer agreements, pricing levels and delivery runs. Those surfaces show that buyers and suppliers search for definitions before they compare software. Porosi uses this page to define the same buying language through a supplier-owned lens: branded apps, web ordering, account context, order-desk review, customer onboarding and finance handoff.
A useful glossary should help a supplier ask better demo questions. If a vendor says "customer portal", does that mean approved trade accounts with the right products and prices, or a generic login page? If a page says "automation", does that mean a reviewable draft, or does it mean the order desk loses control? If a platform promises an ordering app, does the buyer remember the supplier brand, or the software vendor?
The wider platform category for replacing calls, email, WhatsApp and spreadsheets with structured buyer ordering and supplier-side review.
The mobile ordering route that helps repeat trade customers build baskets quickly under the supplier brand.
The browser route for approved customers who order from a desk, laptop or shared venue computer.
Software that lets trade customers place orders directly with a supplier while giving staff a controlled order workflow behind the buyer screen. In food wholesale, the important test is whether the system keeps account pricing, product visibility, quantities, notes, delivery context and finance preparation connected after checkout.
A mobile app used by approved trade buyers to place repeat orders. A serious app should support favourites, search, order history, notes and account context. A supplier-owned app also keeps the supplier brand in front instead of pushing customers into a marketplace identity.
A supplier ordering portal is a web ordering surface for customers who prefer a browser. The portal should not be a public ecommerce shop by default. For wholesale, it usually needs approved accounts, customer-specific pricing, delivery rules, private product ranges and order history.
A white-label ordering app carries the supplier name, logo and buyer experience rather than the software vendor becoming the memorable brand. The operational detail matters: app branding should still connect to web ordering, supplier dashboard review, customer support and finance handoff.
Pricing that changes by customer, account, tier, contract, negotiated list or product group. This is one of the main differences between wholesale ordering and consumer ecommerce. Buyers should see the right price before the order is submitted, and staff should be able to explain where that price came from.
A private catalogue view where each customer sees the products, pack sizes, availability, substitutions and specials that are relevant to their account. See the Porosi page on customer-specific product catalogue workflow for the deeper buying question.
A pricing level is a customer grouping that controls the base price list or discount logic shown to buyers. Suppliers use it when different customer groups have different commercial arrangements. In a demo, ask whether pricing levels are visible enough for staff to support customers without digging through spreadsheets.
A minimum order amount is the smallest order value a customer must reach before checkout, freight terms or delivery rules apply. For suppliers, the rule should be clear before the buyer submits the order, because late surprises create calls and corrections.
A customer agreement is the commercial and operational setup for an account: active status, price level, payment terms, delivery run, customer code, freight rule, order notes and support context. It is not only a contract document. In ordering software, it is the set of rules that shapes what the buyer can do.
A trade account is an approved customer relationship with supplier-specific products, prices, terms and ordering access. Wholesale ordering platforms should treat this account as the centre of the workflow, because two buyers can order the same product but need different pricing, delivery instructions or invoice details.
Pack size describes how a product is ordered and fulfilled: each, case, box, tray, kg, bag, bottle or another unit. Clear pack-size ordering reduces the risk that a buyer enters "2" and the supplier has to guess whether that means two units, two boxes or two kilograms.
Availability is the product status a buyer and staff member rely on before fulfilment. In fresh food, availability can change quickly. A practical ordering workflow should make product visibility, notes and substitution handling clear enough for the supplier to review exceptions before picking or delivery.
The supplier team that receives, checks, adjusts and routes customer orders. A modern order desk may handle app orders, web orders, phone calls, emails, WhatsApp messages, PDFs and salesperson requests in the same morning. The question is whether software removes retyping or simply adds another queue.
An order cut-off is the latest time a customer can place or amend an order for a delivery date. The rule protects picking, purchasing, production and transport planning. A good buyer experience shows cut-off expectations clearly and gives staff enough context for exceptions.
A delivery run groups customers into a route, area or schedule. It matters because the order is not complete just because the basket was submitted. Delivery context affects cut-offs, fulfilment pressure, customer notes, minimums and staff follow-up.
Order review is the supplier-side check that happens before fulfilment or invoice preparation. Staff may confirm unavailable products, changed quantities, notes, customer terms or delivery timing. Porosi treats review as part of the ordering workflow rather than an afterthought.
An invoice-ready order is an order with enough clean product, quantity, price, customer and tax context for finance work to begin with less rekeying. It is not the same as an invoice. It means the order data is structured enough to support Xero, QuickBooks or another finance workflow.
A manual channel is any route where staff still interpret the order: phone, voicemail, email, text, WhatsApp, spreadsheet or attached PDF. Manual channels often stay in the business, but the repeat work should move toward structured ordering when customers are ready.
AI order capture can be useful when customers still send orders through email, WhatsApp, SMS, voicemail or PDF. The operational question is what happens after extraction. Suppliers need a draft they can review, customer context they can trust and a migration path that moves repeat buyers into app and web ordering over time.
AI order capture reads an unstructured order source and turns it into a draft or structured order. For wholesale suppliers, it should preserve human review and account context because product names, pack sizes and substitutions can be ambiguous.
Purchase order automation converts customer POs into a supplier workflow. The useful version does not only parse a document. It checks the customer, product names, codes, quantities, delivery notes and whether staff need to resolve exceptions.
Replacing WhatsApp orders means moving routine repeat baskets into a structured app or web route, while keeping personal support for exceptions. The target is fewer message threads, clearer product data and less office retyping.
Customer onboarding is the practical work of moving approved buyers into the new ordering habit. It includes user invites, product confidence, account pricing checks, support scripts, reminder timing and feedback from the order desk.
Buyer adoption measures whether customers actually place useful repeat orders through the new channel. Adoption is not the same as downloads or invitations. Suppliers should track who ordered, what they ordered, what still arrived manually and where buyers needed help.
A business case compares the current cost of manual orders, missed context, corrections, customer follow-up and invoice cleanup against the rollout cost. Use the wholesale ordering software business case page when you need the decision framework.
A demo scenario is a real order day used to test software. Bring one easy repeat order, one awkward order with notes or substitutions, one account with special pricing and one finance handoff. The wholesale ordering software demo page explains what to bring.
Wholesale ordering software is the full workflow around buyer ordering, account pricing, order review and finance handoff. A customer portal is usually one buyer-facing route inside that workflow, often used from a browser by approved trade customers.
Customer-specific pricing matters because wholesale buyers often have negotiated prices, tiers, product access or account terms. If the wrong price appears before checkout, the order desk inherits the correction later.
No. AI order capture can help with manual channels that remain, but repeat customers should still be moved toward structured app and web ordering where product, price and account context are clearer before submission.
Use the terms as a checklist. Ask how the product handles customer agreements, pricing levels, minimum order amount rules, delivery runs, order cut-offs, manual channels, review workflow and invoice-ready order data.
Use this glossary as the agenda: customer-specific pricing, delivery runs, order cut-offs, manual channels, app adoption, portal access and invoice-ready handoff.