synclane.webkodingtheme.comLive

No signup. Try it with a test card; the demo resets itself regularly.

Most Square connectors match products by title. Rename something, run the sync from a second machine, or let two runs overlap, and you get a second copy of your whole catalogue. If you have watched that happen, you already know what this plugin is for.

SyncLane keeps its own mapping table — one row per product, variation and order, holding the WooCommerce id, the permanent Square id, the object version, the SKU and a content hash. Every write goes through the stored id, so running the sync twice updates the same items instead of duplicating them.

Reading Square into WooCommerce is free and published on WordPress.org. This purchase is the other direction: WooCommerce written back to Square, Square sales imported as orders, and a webhook so both travel in seconds rather than on a 15-minute sweep. Both plugins are in the download, so you can start from either one.

What you get, before you pay

Everything in the box, so there is nothing to discover after checkout.

Files

  • synclane.zip, installed from the WordPress admin
  • Unminified source, no obfuscation
  • Changelog and sample data

Licence

  • 1 WordPress site
  • Licence key sent by email after payment
  • GPL v2 or later

Updates and support

  • 1 year of updates and email support
  • After that the software keeps working
  • Renew only if you want new versions

Requirements

  • WordPress 6.0+
  • WooCommerce 7.0+
  • PHP 7.4+
  • Square API
  1. 1
    Connect Square

    Your own Square application credentials. The mapping table is built on first sync.

  2. 2
    Adopt what already exists

    Matching by SKU, so the first run does not duplicate a catalogue you already have on both sides.

  3. 3
    Choose a direction and let it run

    Products, prices and stock synced the way you chose, keyed by permanent Square id.

What it does

  • Products, variations, prices and SKUs synced one way, in the direction you choose
  • Stock levels kept correct on both sides after a sale on either
  • A mapping table keyed by permanent Square id — never by product name
  • First sync adopts products that already exist on both sides, by SKU
  • Content hashing skips records that have not actually changed
  • HPOS-compatible, with a webhook for near-real-time updates

What you need

  • WordPress 6.0 or newer, WooCommerce 7.0 or newer, PHP 7.4 or newer
  • A Square merchant account, and an application in the Square developer dashboard for the API credentials
  • A publicly reachable site URL if you want the webhook for near-real-time updates
  • SKUs on your products, if you want the first sync to adopt items that already exist on both sides

Runs on your own WordPress and talks to your own Square account. Nothing routes through us.

Why this exists

What SyncLane does not do

  • It syncs products, variations, prices and stock. Customers, orders and order history are not synced.
  • It does not support Square Appointments, Square Loyalty or Square Marketing. The catalogue and inventory are the scope.
  • It does not give you a Square account. You bring your own merchant account and your own application credentials.
  • The webhook needs a publicly reachable site. On a local or firewalled install the scheduled sync still runs; near-real-time does not.

Questions

Why do other Square connectors duplicate my catalogue?

Because they match by product title. Rename something, run a sync from a second machine, or let two runs overlap, and the connector cannot tell an existing product from a new one. SyncLane keeps its own mapping table keyed by the permanent Square id, so a second run updates rather than duplicates.

What happens on the very first sync?

It adopts. Products that already exist on both sides are matched by SKU and written into the mapping table instead of being created again — which is the moment most connectors do their damage.

Which direction does stock move?

You choose the direction for the catalogue. Stock is kept correct on both sides after a sale on either, which is the case that actually matters at a till and a website at the same time.

Do I need a Square account of my own?

Yes, along with an application in the Square developer dashboard for the credentials. There is no shared account and we never see your data.

Does it hammer the Square API?

No. Records are content-hashed, so anything that has not actually changed is skipped, and a webhook handles near-real-time updates instead of constant polling.

Everything else is in the SyncLane documentation, and anything it does not answer goes to support@webkoding.com.

Not quite it? Three nearby

Not ready to buy?

We will write when there is a new plugin, or a release worth knowing about. A few emails a year, each about something we actually shipped — no offers, no sequence, and your address goes nowhere else.

One click to leave, from any of them. What we do with it.