Clover Station (Solo and Duo) is the flagship Clover countertop POS — a 14-inch primary display, optional customer-facing screen, full-size receipt printer, and the central hub for most multi-device Clover deployments. If you're connecting a Station to a WooCommerce store, this guide covers the full setup, the device-specific behaviour around kitchen printer routing and the customer-facing display, and the operational patterns that scale at the higher transaction volumes Station setups usually run.
What Clover Station does well for WooCommerce merchants
Station is the right Clover device when your physical operation is fixed, your transaction volume is moderate to high, and you need a single dominant POS surface for staff. Full-service restaurants, grocery and convenience, established retail, salons, anywhere with a steady stream of in-person sales — Station is the workhorse.
For WooCommerce integration, Station's strengths are throughput and printer flexibility. The on-device Orders app handles a larger catalog and busier order list than Mini comfortably. Station setups also typically include peripheral kitchen printers, label printers, or cash drawers — all of which CloverWoo can route online orders to via Order Routing settings.
Station Solo is a single-screen primary display. Station Duo adds a customer-facing 7-inch screen — useful for showing the in-progress sale, soliciting tips, capturing email for receipts, or surfacing the WooCommerce online order that customer placed earlier when they come in for pickup.
Prerequisites
- A Clover Station (Solo or Duo) on an active Clover merchant account (Sandbox works for testing).
- Wired ethernet (recommended) or stable WiFi to the Station hub.
- A WordPress site with WooCommerce installed (HPOS recommended for higher order volumes).
- Admin access to your Clover developer dashboard and WordPress admin.
- Optional: kitchen printer(s) and/or label printer paired with the Station — note their device IDs from Settings → Printers before starting.
Step 1: Inventory your Station environment
Station setups are usually the most complex Clover environment because of attached peripherals. Before connecting CloverWoo, write down what's actually connected: kitchen printer model and IP, secondary receipt printer if any, label printer for prep tickets, cash drawer behaviour, and whether the Duo's customer-facing display is in use.
On the Station: Settings → Printers → note each printer's name and assignment. Settings → About → confirm merchant ID. The printer list is what CloverWoo's Order Routing screen will show you when you pick a print destination for online orders.
Step 2: Install CloverWoo in WordPress
Standard install: Plugins → Add New → Upload zip → Activate. Station-driven shops often have a larger WooCommerce site with more existing plugins — check that the CloverWoo activation didn't conflict with any existing payment, sync, or inventory plugin. If you were previously running another Clover plugin (QuickSync, Zaytech's gateway, SKU IQ, etc.), see the relevant comparison page for migration notes.
Step 3: Create the Clover developer app + OAuth
Same OAuth flow as every Clover device — but Station setups are often production from day one, so make sure your Clover developer app is configured for the production environment, not just Sandbox. Open dev.clover.com → Apps → your CloverWoo app → environment selector. Permissions needed: Read/Write Inventory, Orders, Customers, Payments.
In WordPress: CloverWoo → Setup → Connect to Clover → sign in → select your Station's merchant → approve. You should see a green 'Connected — Production' state. If you connect to Sandbox first, switch to Production once you've verified sync end-to-end with test orders.
Step 4: Bulk import the catalog
Station catalogs are typically the largest of any Clover device — full restaurant menus (500+ items with modifier groups), grocery catalogs, multi-category retail. The bulk import handles up to roughly 10,000 SKUs in a single pass; for catalogs above that, the import paginates automatically and may take 10–30 minutes.
After import: WooCommerce → Products. Spot-check a few products — verify SKUs, prices, modifiers, categories all came over. Modifier groups in Clover map to WooCommerce product attributes. Categories nest the same way they did in Clover.
Step 5: Register webhooks for real-time sync
CloverWoo → Webhooks → Register webhooks with Clover. From now on, every in-person sale on the Station decrements WooCommerce stock in real time. Every online sale on WooCommerce decrements Clover stock and creates a Clover order in the Orders app on the Station.
Step 6: Configure Order Routing for kitchen / label / receipt printers
This is the most important Station-specific step. Open CloverWoo → Order Routing. You'll see every printer the Station knows about. Decide where online orders should land:
- Restaurant pattern: kitchen printer for prep tickets, optional receipt printer for the counter, no label printer involvement.
- Retail pattern: Station receipt printer for proof-of-online-order, optional label printer for shipping labels (if you fulfil online orders from the same physical location).
- Hybrid (cafe-style) pattern: kitchen printer for food items, Station receipt printer for the customer-facing copy, label printer for to-go bags.
You can route different order types to different printers. CloverWoo's routing rules look at the WooCommerce order type (dine-in, takeaway, delivery, in-store pickup) and the product categories to decide where to print.
Clover Station-specific quirks worth knowing
Customer-facing display (Duo only)
Station Duo's customer-facing screen can display in-progress sales, tip prompts, and email capture for receipts. CloverWoo does not currently push WooCommerce order context to that screen for in-store pickup scenarios — if a customer comes in to collect a WooCommerce online order, staff still need to look it up on the primary screen. This is a known limitation we're tracking.
Station as the hub for peripheral devices
If your Station is also acting as the network hub for Mini terminals at other counter positions, all those devices share the same Clover merchant — and therefore the same CloverWoo connection. You connect once at the merchant level, and every connected Clover device sees the same catalog and online orders.
High-volume queue behaviour
Station setups tend to run high transaction volumes — sometimes 200+ in-store transactions per hour at peak. CloverWoo's queue is designed to handle this, but the default WordPress cron behaviour can lag on shared hosting. If you see online orders printing slightly delayed during peak service, switch to a real system cron (vs WP-Cron) so the queue worker runs every minute regardless of front-end traffic.
HPOS is strongly recommended
WooCommerce High-Performance Order Storage (HPOS) handles higher order volumes much more efficiently than the legacy post-table-based order storage. Station-driven shops should enable HPOS via WooCommerce → Settings → Advanced → Features. CloverWoo is fully HPOS-compatible.
Next steps after setup
- For restaurants: Clover + WooCommerce for restaurants.
- For retail: Clover + WooCommerce for retail.
- Auto-print details: auto-print orders setup guide.
- Order sync deep-dive: order sync complete guide.
- If inventory drifts at high volume: inventory mismatch playbook.
Frequently asked questions
Does CloverWoo work the same with Station Solo and Station Duo?
Yes. Both share the same Clover API surface and the same Orders app. The only difference is the customer-facing screen on the Duo — and CloverWoo doesn't currently push WooCommerce-specific UI to that screen, so the integration behaves identically on both devices.
Can I route online orders to different printers based on item type?
Yes. CloverWoo → Order Routing → Rules lets you route by product category (food → kitchen printer, drinks → bar printer, retail items → counter printer) or by order type (dine-in vs takeaway vs delivery). The rules engine evaluates each online order at print time.
What if my Station also has Mini terminals connected as secondary registers?
Clover treats them all as one merchant — they share the same catalog, customer base, and Orders app. CloverWoo connects once at the merchant level and sees all devices. You pick which device receives the auto-print for online orders, and the rest just see the orders normally.
Do I need HPOS enabled to use CloverWoo on a Station?
Not strictly required, but strongly recommended for Station-volume shops. HPOS (High-Performance Order Storage) handles higher order throughput more efficiently than the legacy storage. CloverWoo is fully HPOS-compatible. Enable it in WooCommerce → Settings → Advanced → Features.
Can I run CloverWoo on a Station that's behind a corporate firewall?
Yes — outbound webhook delivery from Clover to your WordPress site is what matters, not the Station's own network. If your WordPress site is publicly reachable on the internet and isn't blocking Clover's webhook IPs, the integration works regardless of what's between the Station and the public internet.