POS Orders

The Orders screen is every sale taken at a POS, and nothing else. Website orders are not here.

That filter is the point. This is the list you check when you want to know what the shop took, not what the whole business took.

Open the screen

Go to DevDiggers Plugins → MultiPOS for FluentCart → Orders.

The columns

Column	What it shows
Order	Order number and customer, linked to the order in FluentCart, and the offline ID for a sale made offline
Status & Date	The FluentCart order status and when it was placed. Hover the status to read the order’s latest note
Revenue	The order total, the payment method, and any amount refunded
Staff Attribution	The cashier, with their photo, and the outlet underneath

Order, Status & Date and Revenue are sortable. Click a heading to reorder.

Staff Attribution

This column is the reason the screen exists.

Every POS order stores the outlet and the cashier who created it. FluentCart has no idea who was standing at the POS, so MultiPOS records it on the order itself.

That is what makes a discrepancy answerable. A refund nobody remembers, a discount nobody authorised, a void at closing time: all of them have a name attached. The cashier’s name links to their cashier screen for staff who may edit cashiers.

Open the order

Click the order number to open the sale in FluentCart. That is where you read the line items, the payment and the notes.

Filters

The row above the list narrows it down. Press Filter to apply, Reset to clear.

• All outlets: One outlet only.
• All cashiers: One cashier’s sales.
• From and To: A date range.
• Over cashier limits: Only orders where a cashier lowered a price or gave a discount above their limit without a manager’s PIN. Sales a manager approved are left out, so this is the list worth checking.

A flagged order carries an Over limit badge, and its note lists each price change and discount.

Results per page

Screen Options at the top right sets how many rows show. It defaults to 20.

Raise it before an end-of-month check. Paging through six pages of orders is how a row gets missed.

What a POS order looks like in FluentCart

Open FluentCart → Orders and POS sales sit alongside website ones, as ordinary paid orders. Each has one line per product, option or custom item, any fees as fee lines and any coupon as an applied coupon.

Physical items on a POS sale are marked delivered, because the customer walked out with them. The order number is the one the POS prints on the receipt, such as #INV-1.

To see POS sales on their own, use this screen rather than FluentCart’s list.

Two things that surprise people

• The address is the shop’s, not the customer’s. POS orders are addressed to the outlet on purpose, because the sale happened there and FluentCart’s tax should follow the shop’s location.
• The status may already be Completed. Initial Order Status under Configuration → General ships as Completed. That is right for a counter sale and wrong if you still have to pack it. Change it there, not here.

Refunds

There are two places to refund a POS order, and they are not equivalent.

From the terminal, with the green Refund button on the order details panel. This is the one to use for a customer standing at the counter: it writes a transaction row, so the drawer count stays right. See How to Refund an Order.

From FluentCart, with the ordinary refund controls on the order screen. MultiPOS does not take a POS order over once it exists, so notes and refunds behave normally. Either way the order shows as partly or fully refunded.

An admin refund writes no transaction row, so cash handed back at the counter is not deducted from the drawer figure. Record it as a manual cash-out on the day it happens, or refund from the terminal in the first place.

A terminal refund with restocking on puts the units back, into the outlet’s own count on a Custom stock outlet.

Where to go next

• Transactions for the payment side.
• Reports for charts across a date range.
• How a POS Sale Works for what created these rows.