Plenty of Sage 300 distributors have a retail counter or will-call desk. Often it runs on a separate retail POS, which means customers, items and sales live in two places, and someone reconciles them at the end of the day.
What a Sage 300 counter needs
- The customer’s account, history and credit at the counter.
- Every item and variant (size, colour) exactly as it exists in Sage.
- Sales that become Sage 300 orders or invoices, not a separate set of numbers.
- An easy way to look up a past sale and issue a credit.
- A clean day-end handoff to Accounts Receivable.
How Metabox POS works
Metabox POS is a front end to Sage 300 Order Entry and Accounts Receivable, so there’s no parallel invoicing system.
- Customer lookup. See the customer code, name, last visit, order count and account or credit totals at the counter.
- Native variants. Sizes, colours and other variants come straight from Sage IC Item Optional Fields. There’s no separate variant database to sync.
- Fast browsing. Favourites, grid or list view and inline product photos (with Metabox Inventory).
- Credits and returns. Find any past sale by date, order number or item number and issue a credit without re-keying it.
- Day-end AR batch. Closing the day creates the AR batch, ready to reconcile in Sage 300 the next day.
What it doesn’t do
Metabox POS doesn’t process card payments. Use it alongside your existing payment terminal: POS handles the sale, variants and AR, and the terminal takes the card. POS also requires Metabox Inventory, which supplies product photos and category browsing.
Learn more
See the Metabox POS page and pricing, or book a demo.