Gorgias on Oliver POS

The Gorgias for WooCommerce connector is one of the more deeply built integrations in the WooCommerce ecosystem — Gorgias was designed around the e-commerce ticket from day one, and the WooCommerce app reflects that. When an agent opens a ticket, Gorgias renders the customer's full WooCommerce profile in the right rail: lifetime order count, lifetime value, average order value, the most recent orders with line items and totals, refund history, customer tags, and any notes attached on the WooCommerce side. Macros and HTTP actions can reference any of those fields directly inside the reply.

The agent can issue a refund on a WooCommerce order from inside the ticket — partial or full, with reason codes — and the refund posts back to WooCommerce as a standard refund action. Order tags, customer tags, and shipping events can drive auto-responses, ticket routing, and SLA timers. Oliver POS writes register sales into WooCommerce as standard orders matched to the existing customer record, so those sales appear in the Gorgias sidebar the same way online orders do. The agent doesn't need a separate Oliver POS app inside Gorgias and doesn't treat in-store sales as a special case in macros or rules.

Gorgias is the helpdesk of choice for DTC and online-first brands that have started opening physical retail — popup, flagship, wholesale showroom, or a small chain of branded stores. The Gorgias team and the brand's support team are usually highly drilled on order-history-driven replies: the first thing the agent does on any ticket is glance at the sidebar, confirm what the customer bought, then reply with the right macro. The whole workflow assumes the order is visible.

When the customer's purchase is in-store and the brand's POS doesn't feed WooCommerce, the workflow snaps. The agent opens the ticket, sees an online order list that doesn't include the relevant purchase, and has to leave Gorgias entirely — log into the POS terminal, find the customer by name, scroll to the right day, copy the receipt details back into Gorgias. The macro arsenal is useless because none of the macros know about the in-store sale. First response slips from minutes to a workday.

Oliver POS writes the counter sale into the WooCommerce customer record Gorgias is already reading. The next ticket from that customer opens with the in-store order in the sidebar — same line items, same totals, same refund-action button — and the agent fires the same macros they always do. The Gorgias workflow that the team trained on doesn't change; it just starts working on counter sales the way it always worked on online ones.

The register-side flow follows the standard Oliver pattern. The cashier rings the sale on Oliver POS, captures the customer at tender by email or phone — matching against the existing WooCommerce customer base, no duplicate created — 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 and reconcile against the original order.

When the customer emails, chats from the storefront widget, DMs from Instagram, or messages from Facebook, the conversation lands in Gorgias. Gorgias matches the conversation to the WooCommerce customer record and renders the sidebar — lifetime metrics, recent orders, refund history. The Oliver-written orders sit in the same list as online orders, with the same fields. The agent opens the order, checks the per-outlet tag, fires a macro that references the order total or the most recent line item, and (where the connector supports it) triggers a refund on the WooCommerce order from inside the ticket. The refund syncs down to Oliver on the next register sync, the original counter receipt is reconciled, and Gorgias and Oliver reporting agree on the numbers.

Gorgias rules can filter on the created_via=pos meta or the per-outlet tag so routing and SLAs distinguish online versus in-store originating sales — for example, sending receipt-and-return tickets to a regional agent group while routing storefront order-status questions to the e-commerce-first team. The macro library doesn't need a counter-specific branch; the in-store sale is just another order in the customer record.

Gorgias on Oliver POS is a natural fit for DTC and online-first brands that have opened physical retail and run a Gorgias-trained support team — apparel, footwear, beauty, jewellery, home goods, specialty food, and similar verticals where the brand prides itself on a single customer relationship across channels. Outlet counts from one popup to a few dozen branded stores; support teams from two agents to a few dozen, often heavily macro-driven. The biggest wins land at brands where the support team currently has to side-trip into the POS terminal every time a counter customer reaches out; Oliver removes that side-trip and lets the existing Gorgias workflow do its job on in-store sales the same way it already does on online ones.