Oliver POS

At the counter, a cashier can scan or search products, take split payments and print a receipt. For a realistic trial, create a small fictional basket with a product variation and a discount, then inspect the resulting WooCommerce order and stock movement.

The mobile register is presented as a way to sell in the aisle or at an event with the same catalogue. Tap to Pay and basket sync are described, but device eligibility and payment availability should be checked in the merchant’s country before relying on a phone as the only checkout.

Oliver says product, customer, stock, order and refund data sync both ways with WooCommerce. Use one sample sale through the web shop and one through the register to check timing, variants, tax and refunds; a marketing claim of real-time sync is not a substitute for that test.

For a network interruption, the vendor says the register caches the catalogue and queues sales until reconnection. Test a fictional offline order, then inspect whether it appears exactly once and whether stock conflicts are surfaced. Offline card authorization is a separate payment question.

The product page describes a shared fulfilment board for web orders and in-store collection. Check how a pickup order moves from paid to ready and collected, and which staff can change its status before enabling customer notifications.

Customer profiles are described across online and counter purchases. Before importing or matching real records, check whether the same person can be found consistently and whether staff access, consent and saved payment options work as intended.

The vendor describes stock visibility by outlet, transfers, end-of-day reports and CSV exports. Multi-outlet inventory is listed in Enterprise on the pricing page, so a shop with more than one location should confirm its tier and test a sample transfer and report.