Tidio on Oliver POS

The Tidio – Live Chat & AI Chatbots plugin links a Tidio workspace to a WooCommerce store and exposes 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 fire pre-chat triggers, 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) issue refunds or write back 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 identically to 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 wire a separate POS connector into Tidio.

Tidio is the live-chat platform smaller WooCommerce stores pick because it covers the same workflows the enterprise platforms do — Messenger-style storefront widget, agent inbox, automations, AI bot — at SMB pricing. The retailers running it usually run one or a small handful of outlets 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 DM. The retailer's job-to-be-done for Tidio is conversational triage at small-business scale.

The blind spot is the same one larger retailers hit, just with sharper consequences because the team is small. If the brand also runs a counter and the POS doesn't feed 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 into the POS terminal, find the customer, copy the receipt — for every counter-purchase chat. At small scale, those minutes add up faster than the team can absorb.

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 live in the same customer object Tidio reads from.

The register-side flow is the same one every Oliver-on-WooCommerce setup uses. The cashier rings the sale on Oliver POS, captures the customer at tender by email or phone — matched against the existing WooCommerce customer base — and tenders. 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 (handoff to agent for refunds, knowledge-base answer for sizing questions, automation 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 fires a refund on the WooCommerce order from inside Tidio, the refund syncs down 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 distinguish online versus in-store originating 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 the enterprise toolchain.

Tidio on Oliver POS suits small WooCommerce retailers — one to a small handful of outlets, a one-to-five-agent support team (often founder-led), and most customer questions arriving through the storefront chat widget. Boutique apparel, beauty, specialty food, hobby and craft, and similar verticals hit this profile most often. The team picked Tidio because it covers Lyro AI and live chat at a price point the business can sustain; the team picks Oliver POS because the counter sale finally feeds the same WooCommerce customer record the chat widget and the bot already read. The result is small-business support that finally feels cross-channel without an enterprise budget.