POS INTEGRATION FOR WOOCOMMERCE

Your register and your website, telling one story.

Custom POS integrations for WordPress and WooCommerce, with Clover running in production today, so in-store sales and online stock stop drifting apart.

Or call or text (502) 387-1142
5.0 32 Google reviews
25+Years building websites
1Person, start to finish
Example · register and website
A sale in one place updates the other
ONE INVENTORY, HOWEVER IT SELLS

One inventory, however it sells

01

Stock that follows every sale

A sale at the counter updates the website, and a sale online comes off the register. No morning spreadsheet ritual.

02

An end to overselling

An item that sells out in the shop stops selling online before a customer buys what you no longer have.

03

SKUs done right first

Most sync problems are catalog problems. I audit and repair SKUs on both sides before wiring anything together.

04

Built on the POS API

A direct integration with the register’s own platform, not a fragile add-on pretending to be one.

05

Subscriptions replaced

Off-the-shelf sync tools bill monthly and match on their terms. A purpose-built plugin does exactly what your catalog needs.

06

Either side can be the master

At Kentucky Peerless the register leads. When your WooCommerce catalog is the master, the sync runs the other way and pushes products and stock to Clover.

A register sale updating WooCommerce stock within a minute, with the sync log below (sample data)
RUNNING IN PRODUCTION

The Peerless gift shop and website share one count.

Kentucky Peerless runs a Clover register in the distillery gift shop and sells the same merchandise online. A custom plugin I wrote talks to Clover’s own platform and keeps the register and the website’s inventory in step, with product matching and clear rules for which system owns each count. It replaced a third-party sync subscription whose quiet mismatches had to be root-caused SKU by SKU. Now the register holds the count: register sales reach the website every hour, and website sales come off Clover within minutes.

The sync is a custom WordPress plugin, and the store it protects is one of the WooCommerce stores I design and run. The store side of this work is on the WooCommerce developer page, and the plugin itself is my work as a WordPress developer in Louisville.

Kentucky Peerless · rebuilt 10-26-2026

Inventory tools built around stock ownership

I built a Clover inventory workflow for Kentucky Peerless with product matching, participation controls, comparison views and reconciliation. The design makes the stock authority and enabled sync directions explicit, including when a result needs review.

Read about the Peerless inventory work →

Stock check comparing register and website counts, with items that need review flagged (sample data)
Sample data, not real stock or sales.
1

Inventory, however it sells

0

Middleman subscriptions

Clover

Running in production today

SKUs

Audited on both sides before anything is wired

TWO CHANNELS, ONE CATALOG

Sell at the counter and online without double entry

The merchandise your staff rings up at the register is the same catalog your website sells. The integration keeps quantities aligned in both directions and leaves your team one list to maintain instead of two. For a shop that sells in person first, it is the core of a retail store website.

Point of sale register screen showing stock counts from the catalog the website shares (sample data)
WooCommerce product page showing the same stock count as the register (sample data)
SYNC TOOLS SELL SUBSCRIPTIONS

Sync tools sell subscriptions. I build fits.

01

Your rules, not theirs

Which products sync, which side wins, what happens at zero: decisions you make once, written into your plugin.

02

A sync you can check

Runs happen on a schedule you set, with results you can inspect instead of taking on faith.

03

One developer, whole stack

The same person maintains the store, the website, and the integration. When something drifts, there is one call to make.

FROM PROBLEM TO SHIPPED SYSTEM

How it gets built here.

01

Audit the catalog

I diff the register against the website item by item before writing code. Sync built on bad SKUs just spreads them faster.

02

Quote it straight

A clear number before work starts. No hourly meter running while you wonder.

03

Build on staging

Developed and tested against real scenarios before it ever touches your live site.

04

Ship and support

Deployed carefully, refined with your staff, and supported by the person who wrote it.

ASKED BEFORE EVERY BUILD

What owners want to know first.

Which POS systems do you integrate?

Clover is running in production today. Square and most modern POS platforms expose APIs I can build against, and the Square side is covered in Square to WooCommerce inventory sync.

Two-way or one-way sync?

Two-way. At Kentucky Peerless the register owns the count: register sales update the website every hour, and website sales come off Clover within minutes. When WooCommerce is your master catalog, I build it the other way: WooCommerce pushes products and stock to Clover, and register sales are read back. If minutes are too slow, Clover’s webhooks can carry a register sale to the website within seconds.

My SKUs are a mess. Is that a problem?

It is the first problem, and it is normal. The audit finds duplicates, mistypes, and orphans on both sides, and I fix them before connecting anything.

What does it cost?

Scoped flat after the catalog audit. No monthly per-store fee to a middleman, ever.

Sync rules choosing whether the register or the website owns the stock count (sample data)
Sync status: in sync, 1,248 items, 0 mismatches, next check 4:00 PM (sample data)
FROM THE SAME WORKSHOP

Systems that already work together.

01

Guest check-in systems

The front-desk board that turns booking-day chaos into a calm list of names.

02

Online booking systems

Live calendars, ticket types, capacity, and payment on your own website.

03

Digital guest books

A branded kiosk that saves every signup to a ledger you own.

RECENT WEB PROJECTS

Systems with users, not demos.

ONE COUNT, BOTH COUNTERS

The counter and the cart should never argue.

Tell me what you sell and where you sell it, and I will map the integration that keeps both sides honest.

Connect with me

Tell me about the project.

What happens next

  1. 01
    I reply, usually the same day. Every message comes straight to me, not a ticket queue.
  2. 02
    A short call. What the site needs to do, who it is for, and what has not worked before.
  3. 03
    A written scope and flat quote. Before any work starts, with hosting and ongoing care listed separately.
Rather talk?(502) 387-1142shaun@shaunwilsondesigns.comMon to Fri, 8am to 6pm

5.0 on Google · 32 reviews · I usually reply the same day