Tidio on Oliver POS

The Tidio – Live Chat & AI Chatbots plugin links a Tidio workspace to a WooCommerce store and shows the matched customer's data inside both the live-chat widget and the agent inbox. When a logged-in shopper opens chat from the storefront, Lyro and the agent see the customer's WooCommerce contact — name, email, phone, lifetime order count, recent orders with line items and totals — pulled into the conversation panel. Tidio automation flows can branch on order attributes (last-order date, last-order total, abandoned cart, refund history) to trigger pre-chat actions, route to the right agent, or open a Lyro flow trained on the store's product knowledge.

Agents can drill into a specific order from inside the inbox, view the receipt, and (on connector versions that support it) process refunds or add order notes to WooCommerce without leaving Tidio. Oliver POS writes register sales into WooCommerce as standard orders matched to the existing customer record, so those sales appear in the Tidio chat and inbox just like online orders. Lyro's suggested answers and the agent's sidebar both see the in-store activity automatically; the SMB retailer doesn't have to set up a separate POS connector into Tidio.

Tidio is the live-chat platform smaller WooCommerce stores pick because it covers the same features as the enterprise platforms do — Messenger-style storefront widget, agent inbox, automations, AI bot — at prices for SMBs. The retailers running it usually run one or a few branches and a small support team (one to five agents, sometimes the founder herself), with most customer questions arriving through the chat widget on the storefront and a smaller stream through email or social media DMs. The main reason retailers use Tidio is to manage customer conversations efficiently, on a small business scale.

The problem is the same one larger retailers face, just with sharper consequences because the team is small. If the brand also runs a counter and the POS doesn't sync with WooCommerce, the chat widget shows no record of the in-store sale the customer is messaging about. Lyro can't answer because Lyro doesn't see the purchase. The lone agent (or the founder) has to switch from Tidio to the POS terminal, find the customer, and copy the receipt — for every chat about an in-store purchase. At small scale, that wasted time adds up quickly.

Oliver POS writes the counter sale into the WooCommerce customer record Tidio is already reading. Lyro sees it. The agent sees it. The same automation that worked for online orders — abandoned-cart triggers, post-purchase follow-ups, refund-flow handoffs — works for in-store sales because they're all stored in the same customer record that Tidio reads from.

The process at the register is the same for any Oliver-on-WooCommerce setup. The cashier rings up the sale on Oliver POS, gets the customer's info (email or phone) during payment — matched against the existing WooCommerce customer base — and processes the payment. Oliver writes the WooCommerce order with line items, taxes, payment method, the created_via=pos meta flag, and a per-outlet tag identifying the store. Refunds at the counter write standard WooCommerce refund actions reconciled against the original order.

When the customer opens chat from the storefront, the Tidio widget loads with the matched WooCommerce contact in the conversation context. Lyro's knowledge-of-the-customer block sees the recent orders — in-store and online — and routes the conversation accordingly (to an agent for refunds, to a help article for sizing questions, or to an automated flow for status updates). The agent inbox renders the same order list in the sidebar, with line items, totals, and refund-action buttons. Where the connector supports it, the agent processes a refund on the WooCommerce order from inside Tidio, the refund syncs to Oliver on the next register sync, and the in-store receipt is reconciled.

Tidio automation rules can filter on the created_via=pos meta or the per-outlet tag so flows can distinguish between online versus in-store sales — for example, sending a post-purchase NPS only to customers whose most recent sale came from a specific outlet, or routing receipt-and-return tickets to a regional agent. The small team gets enterprise-style cross-channel context without enterprise-level tools.

Tidio on Oliver POS is a great fit for small WooCommerce retailers — with one to a few branches, a one-to-five-agent support team (often led by the founder), and most customer questions arriving through the storefront chat widget. This often includes retailers in boutique apparel, beauty, specialty food, hobbies and crafts, and similar industries. The team picked Tidio because it covers Lyro AI and live chat at a price the business can afford; the team picks Oliver POS because the in-store sale finally syncs to the same WooCommerce customer record that the chat widget and the bot already read. The result is customer support that feels connected across all channels, without needing an enterprise budget.