Operations·16 November 2026·16 min read

POS with Website Integration: The Complete Buying Guide

How to connect a POS to your sales website or online store: what syncs, three ways, the source for each data type, costs and faults. WooCommerce, Shopify, Wix.

Written with AI assistance and fact-checked against sources

A boutique owner packing an online order on the counter while a customer pays at the register in the background

A business that sells both in a shop and on a website is really managing one stock in two places. Until the two are connected, someone updates by hand, and sooner or later this happens: a customer pays online for the last dress in size M, which sold in the shop an hour earlier. Or the reverse: the website shows "sold out" for an item that is sitting on the shelf. A POS with website integration fixes this: a sale in the shop lowers stock on the website, an online order lowers stock in the shop, and both sides show the same product and the same price.

But "website integration" can mean three completely different things, with different costs, different responsibilities and different points of failure. This guide explains exactly what gets connected, in which ways, which system should be the source for each type of data, who does what, what it costs and what can go wrong. It is useful whichever POS you choose, and for any online store: WordPress with WooCommerce, Shopify, Wix, a custom-built site, and a WordPress site that does not sell yet.

In short

  1. You connect six layers of data: stock, products, prices, customers, orders and reports. You don't need all of them on day one.
  2. There are three ways: the POS and the online store in the same system; connecting the POS to your existing online store (WordPress with WooCommerce, Shopify, Wix or a custom site) through an API or a plugin; or a sync tool that sits in the middle.
  3. The most important decision: each type of data has exactly one system that is the source. Usually stock, products and prices are managed in the POS, and photos and descriptions on the website.
  4. Sync speed and reserving the item during checkout decide whether you sell the last item twice.
  5. A receipt for a website order is issued by one system only: the one that charged the customer.

What you connect between the POS and the online store: six layers of data

When a vendor says "we have website integration", ask: integration of what? These are the six layers, each with its own direction and its own risk:

Layer What moves Common direction What happens without integration
Stock How many of each product, size and color Both directions You sell online an item that already sold in the shop
Products Name, barcode or SKU, sizes, colors, category POS to website A new product in the shop doesn't appear on the website, or appears twice
Prices and promotions Selling price, promotion, a different price per channel POS to website A customer sees a different price online than on the shelf
Customers Name, phone, email, marketing consent, loyalty points As needed The same customer is registered twice, and points don't carry over
Orders What sold online, at what price, pickup or delivery Website to POS Shop stock doesn't go down, and there is no single picture of sales
Reports Sales and returns by channel Into one place Two reports that don't match, and double work for your accountant

You don't have to connect everything on day one. Most of the pain is in stock and products, so start there. Customers and reports can be added in a second stage, once the base works.

Three ways to connect a POS to a sales website

Way 1: POS and online store in the same system

There is no integration here, because there aren't two systems. Product, stock and price live in one place, and the online store is just another sales channel of the POS.

  1. Fits: a business that doesn't have an online store yet, or whose current website is small and doesn't sell much.
  2. Advantage: nothing can break between two systems, and you don't need a developer.
  3. Disadvantage: the store is limited to what the POS vendor built. Design, payment options and shipping are what they are.

For example, KupaLi's Smart POS plan at ₪119 includes a built-in online store: customers pay at pickup or through a payment link that you send. For a business starting to sell online this is often enough, with no project needed.

Way 2: connect the POS to an existing website, through an API or a plugin

An API is a proper "door" that the POS opens to the website. Through it the website reads products and stock, reserves an item for a customer during checkout, and receives a notification about every sale. A plugin is a ready-made connection to a specific platform, for example WooCommerce, which you install and configure without writing much code.

  1. Fits: a business that already has a sales website and doesn't want to rebuild it.
  2. Advantage: the website stays yours, with your design, your SEO and the payment provider you chose. Updates are fast, because they pass directly between the systems.
  3. Disadvantage: someone has to build the connection and maintain it. When the website platform changes, the connection has to change with it.

A real example of such a change: Shopify announced that its old REST interface became "legacy" on October 1, 2024, and that from April 1, 2025 every new public app must be built on its GraphQL interface. A connection built a few years ago may need work even though you touched nothing.

Way 3: a sync tool in the middle

Tools like Zapier or Make, or a dedicated sync service, sit between the POS and the website and work by rules: "when an item sells in the POS, update the quantity on the website".

  1. Fits: simple, low-volume connections, for example moving a new customer from the POS to the mailing list.
  2. Advantage: quick to set up, sometimes without a developer.
  3. Disadvantage: another system, another subscription and another place that can get stuck. And the speed depends on the tool and the plan.

Two Zapier numbers illustrate this. Speed: on most triggers the tool checks for something new every 15 minutes on the free plan, and every 2 minutes on the Professional plan. A quarter of an hour is a long time when one item is left. And pricing by actions: the free plan includes 100 actions a month, and the basic paid plan includes 750 actions at $19.99 a month on annual billing. A shop with 30 sales a day reaches 900 actions a month on stock updates alone. Make's free plan includes 1,000 credits a month.

The three ways in one table

One system API or plugin Tool in the middle
Who it fits A business with no website, or a simple one A business with an existing website that sells A small, simple connection
Needs a developer? No Usually yes. With a plugin, sometimes not Sometimes
Update speed Instant, it's the same system Depends on the integration. Good: seconds Depends on the tool and plan, sometimes minutes
What you pay for POS subscription Subscription, development and maintenance POS subscription and a per-action tool subscription
What can break Little The connection, when something changes on either side The tool, the monthly quota, the settings

The important decision: which system is the source for each piece of data

It's easy to skip this decision, and then you pay for it. The source is the system where the data is changed. The other system only receives a copy.

When the same field can be edited in both systems, they overwrite each other. Example: in the morning you lower a shirt's price in the POS to ₪89. At noon someone updates it on the website to ₪99, because they didn't know. At night a sync runs, and one of the prices disappears. Which one? It depends which ran last. The platforms themselves fight this: in Wix, to update stock through the API you must send the item's current version number, precisely so an old update doesn't overwrite a new one.

Our recommendation for most businesses:

Data Source Why
Stock quantity The POS. The website reports every order to it That's where you receive goods, count and sell from the shelf
Product: name, barcode, sizes, colors The POS That's where you scan, and where a new product is created when goods arrive
Price, including a different price for the website The POS One price, managed in one place, even when it differs per channel
Photos, descriptions, text for Google The website The POS doesn't need them
Cost price and suppliers The POS only Should never leave it
Customers Wherever the customer registered. Match by mobile number, with email as backup This way the same customer isn't created twice
Website orders The website The POS receives a copy, to lower stock and for reports
Receipt for a website order The system that charged the customer Once only

Rule of thumb: two-way sync only for stock, and for customers if needed. For everything else, one direction and one source.

An employee scanning a barcode on a mug in the back room of a homeware shop, next to boxes of new stock

How it looks on WordPress, Shopify, Wix and a custom-built site

The platform of your online store determines how you connect and what to check. What's worth knowing about each:

  1. WordPress with WooCommerce: WooCommerce is the store plugin for WordPress. It's free and open source, and has a built-in API. You create an API key in the settings and set it to read, write or read/write. The notifications the website sends out (webhooks) can be signed, so the other side knows they're genuine. Two things worth knowing: after 5 consecutive delivery failures WooCommerce disables these notifications, and by default it holds stock for an unpaid order for 60 minutes before the order is cancelled.
  2. A WordPress site that doesn't sell yet: there are two ways. You install WooCommerce from the plugins menu in the dashboard (search, install and activate, and the setup wizard opens), then connect the store to the POS as in the previous section. Or the developer connects the website directly to the POS API, as with a custom-built site.
  3. Shopify (as the website): you connect through an app or through the API, and a new public app must work with the GraphQL interface. Stock is counted per location, and units that were ordered but not yet shipped are counted as "committed" and aren't sold again. Notifications are signed. If they fail, Shopify retries 8 times over 4 hours, and a webhook subscription created through the API is deleted after 8 consecutive failures. Shopify also notes that the same notification can arrive more than once, so the integration must detect duplicates.
  4. Wix: you connect through the Wix API with a key you create in the account settings, and choose its permissions. Every stock item in Wix is a combination of a variant and a location, and every update must include the latest version number. According to Wix's documentation, the quantity can drop below zero when stock is deducted for an order that was already paid. In other words, even the platform acknowledges that a double sale can happen.
  5. A custom-built site: any integration is possible, but all the maintenance is on you. Ask the developer up front who fixes things when something breaks, after the project is closed.

Who does what: the POS vendor, the developer and you

A website integration is the work of three parties, sometimes four. When it's unclear who is responsible for what, every fault turns into finger-pointing.

  1. The POS vendor: provides a stable, documented API, keys with limited permissions, a notification on every sale and change, and support for the developer.
  2. The developer or website builder: connects the website to the API, matches products between the two systems, builds the reservation on the checkout page, and tests.
  3. The website's payment provider: charges the customer. Credit card numbers should not pass through the POS or through your server. Under the card security standard (PCI DSS), a business that wants the simplest validation path does not store, process or transmit card data on its own systems.
  4. You: decide which system is the source for each piece of data, sort out barcodes, and check after go-live.

Ask the developer and the POS vendor for a one-page document: what each party does, and who to call when something doesn't update.

What it costs and how long it takes

What you pay for

  1. POS subscription. Check whether the website integration is included, a monthly add-on or a one-time payment.
  2. Development. A one-time payment to a developer. Ask for a fixed price against a written list of what gets connected, not an open-ended "by the hour".
  3. Maintenance. Developer hours when the website platform or the POS changes version. Ask how much it cost other customers in the past year.
  4. A tool in the middle, if you chose way 3: a subscription by number of actions, which grows with sales.
  5. The website itself: hosting, template and plugins. The integration doesn't change them, but a connector plugin may cost extra.

With way 1 most of these lines simply don't exist. That's its big advantage.

How long

You can't give a single number of days, because the time depends mostly on the state of your catalog. These are the stages, in order:

  1. Mapping. Write down what you connect, in which direction, and which system is the source for each piece of data (the table above).
  2. Catalog cleanup. Every product, and every size and color of it, gets a unique barcode or SKU, identical in the POS and on the website. This is the stage that's easiest to underestimate. A clothing shop with 200 styles, 4 sizes and 3 colors has 2,400 items that each need their own code. We wrote a separate guide on this: Barcodes for a small business: a catalog without duplicates.
  3. Development in a test environment. Not on the live website.
  4. Testing. At least the scenarios in the list below.
  5. Stock count and go-live at a quiet hour, so that the first number that reaches the website is correct.
  6. A week of monitoring. Every day, compare a few sample items in the POS and on the website.

Seven tests before you go live

  1. In the shop, sell an item that has one unit left. How long until it's marked "sold out" on the website?
  2. Order on the website. Did the stock in the POS go down?
  3. Start a checkout online for the last item, and at the same time sell it in the shop. What happens?
  4. Change a price in the POS. When does it update on the website?
  5. Create a new product with sizes and colors. Does it appear on the website correctly, and not twice?
  6. In the shop, return an item bought online. Does stock go back, without a double sale being recorded?
  7. Disconnect the internet in the shop for a quarter of an hour, make sales, and reconnect. Does everything reach the website?

What can go wrong, and how you'll know in time

Fault Why it happens What prevents it
The last item sells twice Sync is slow, or there's no reservation during checkout Sync in seconds, reservation at checkout and a safety margin on the website
A product appears twice on the website No shared code for the same product in both systems Match by barcode or SKU before the first import
The integration stopped working and nobody noticed Failed notifications are disabled after a few attempts An automatic alert when there's no update for a while, and a log you can check
The same sale was recorded twice The same notification arrived twice Duplicate detection on the receiving side
The customer got two receipts Both the website and the POS issued a receipt Only one system issues a receipt for a website order
A different price on the website and on the shelf Price can be edited in both systems One source for price
Sales didn't reach the website The internet in the shop went down A POS that keeps selling offline and syncs when it's back

We wrote about the internet going down in the shop in detail: Online or offline POS: what happens when the internet goes down?

A short decision tree

  1. No online store, or the website barely sells? A POS with a built-in online store (way 1).
  2. A website that sells, and a developer or website builder who works with you? Connect through an API (way 2).
  3. The website is on WordPress with WooCommerce, Shopify or Wix, and there's a ready plugin? Check who wrote it and who maintains it, and only then decide (way 2).
  4. A WordPress site that doesn't sell yet? Add WooCommerce and connect it to the POS, or connect the website directly to the POS API (way 2).
  5. Need only a small connection, for example new customers to a mailing list? A tool in the middle may be enough (way 3).
  6. Selling single items, expensive items or low stock? Speed and reservation are critical. Way 1 or 2 only, not a tool that checks every quarter of an hour.

One stock for the shop and the website

This is the part where most businesses feel the difference. The questions that decide whether you sell an item twice: how long it takes for a shop sale to reach the website, whether the item is held for the customer while they pay, and how many units to hide on the website as a safety margin. And there are sizes and colors, returns that go back to stock, multiple branches, and in-store pickup.

It's all in the guide: One stock for the shop and the website: how not to sell the last item twice.

Products and prices: where you manage the catalog

A new product created in the POS needs to appear on the website, but without duplicates and with the photos and descriptions that only the website needs. You need to decide whether sync goes one way or two, how to import an existing catalog the first time, how to manage a different price for the website and a promotion for the website only, and what to do with a product that left the range. And cost price? It doesn't leave the POS.

It's all in the guide: Products and prices: where you manage the catalog.

Customers, orders and returns

A customer who buys both in the shop and on the website should be one customer in the system, with the same loyalty points and the same gift card. There's also returning a website purchase in the shop, credits, and what goes to your accountant. As for receipts, the rule is simple: according to Kol Zchut, a business owner must issue a receipt immediately upon receiving payment. So whoever charges the customer on the website is the one who issues the receipt, and the POS only records the sale. Two receipts for the same sale is a mess in the books.

It's all in the guide: Customers, orders and returns: shop and website in one picture.

What to ask the POS company

Before you sign, ask the POS vendor about sync speed, reservation during checkout, which platforms are supported, who maintains the connection when it breaks, what happens when there's no internet, what it really costs, who owns the data and how you leave, and how the connection is secured. We prepared a list of 26 questions, with what a good answer sounds like and what should raise a red flag.

The full list, for printing: Questions to ask a POS company before connecting to a website.

A cosmetics shop owner on the phone, checking items off a printed list at the counter

How KupaLi connects to a website

KupaLi is a cloud POS that runs in the browser, on a computer, tablet or phone you already have. There are two ways to connect it to a website:

  1. A built-in online store on the Smart POS plan: customers pay at pickup or through a payment link that you send. No integration to build.
  2. **POS with API** for an existing sales website. The API works with any programming language and any server, so a developer can connect it to a WordPress site too, with or without WooCommerce. A sale, price change or stock update in the POS reaches the website within about 5 seconds. When a customer pays on the website, the item is held for them for 10 minutes (adjustable). If it still sells in the shop, the website gets a notification and can contact the customer. Products are managed in the POS, and the website receives them with the price, photo, sizes and colors. Sales, returns and new customers are sent to your systems.
  3. Security: a separate key for each system, with permissions only for what it needs, and you can revoke it with one click. Every update sent to the website is signed. Cost prices, minimum prices and employee details don't leave the POS.
  4. Receipts: the POS doesn't issue a receipt for a website order. The website charges and sends the receipt, and the POS updates stock and records what sold and at what price.

Need something that isn't listed here, for example products created on the website that flow to the POS, loyalty points in both channels or in-store pickup? That can be connected too. We connect according to what the business needs. The API price depends on what gets connected: write to us and we'll come back with a quote.

The plans: Register at ₪79 and Smart POS at ₪119, per branch per month, before VAT. No setup fee and no commitment. Details on the pricing page and the home page.

Want to see how it works? Start 14 days free, no credit card.

This information was checked in November 2026 and is general. Platforms and prices change; before deciding, ask for a written quote and check with your developer and your accountant.

This article is based on publicly available information. Found a mistake? Write to us at support@kupali.co.il and we will fix it.

What else do people ask?

What is a POS with website integration?

A POS connected to your sales website or online store, so a sale in the shop updates stock on the website, and an order on the website updates the POS. You can also connect products, prices, customers and reports.

Can I connect a POS to a WordPress, Wix or Shopify site?

Yes. Each of them has an API through which you connect stock and products. On WordPress it's usually the WooCommerce API, the WordPress store plugin. A WordPress site that doesn't sell yet? Add WooCommerce, or connect it directly to the POS API. Check who builds the connection and who maintains it.

How fast does website stock update after a shop sale?

It depends on the way you connect. With a good API it's seconds. A sync tool that checks on a schedule updates only every few minutes. With Zapier, for example, every 15 minutes on the free plan and every 2 minutes on Professional. Selling single items? Look for seconds.

Do I need a developer to connect a POS to an online store?

With an API connection, usually yes. With a ready plugin, sometimes not. With a POS that has a built-in online store, you don't need any integration at all.

Who issues the receipt for a website order?

The system that charged the customer, usually the website or the invoicing system connected to it. The POS records the sale and lowers stock, but doesn't issue a second receipt.