Products and Prices: Where to Manage the Catalog With a POS and an Online Store
One catalog for your POS and online store: field ownership, barcode matching, first import without duplicates, website price, promotions, VAT, retired items.
Written with AI assistance and fact-checked against sources
On Sunday morning you raised the price of a ceramic mug in the POS from ₪39.90 to ₪44.90. On the website it stayed ₪39.90. On Wednesday a customer walks into the shop with her phone in hand, shows the price on the website and asks why it's more expensive in the shop. In another case, someone creates "Large blue mug" on the website, and in the POS it already exists as "Blue ceramic cup 400". After the integration you have two products, two stocks, and neither is right.
Many problems when connecting a POS to a sales website start with the catalog, even before stock: which product is which, where a new product is created, who sets the price, and what happens to fields that exist on only one side. This guide goes through these decisions one by one, with examples, so you know what to ask the developer and what to ask the POS vendor.
In short
- Each type of data has one owner: price and stock usually in the POS, photos and descriptions on the website. Whatever isn't defined gets overwritten.
- Connect products by barcode or SKU, never by name. Matching by name is the fastest route to duplicates.
- Before the first import: export both catalogs, match by barcode, and test on 20 products before the rest.
- Choosing a different price on the website and in the shop? The price shown to the customer is binding, and it must include VAT.
- Cost price never leaves the POS. A product taken off the shelf is marked inactive, not deleted.
One rule: every type of data has an owner
The most important decision in an integration isn't technical: for each field, which system decides and which only receives. Without such a decision, every update on one side can overwrite an update on the other, and it will look like a random bug.
This is how it looks in most businesses that sell both in-store and online:
| Field | Recommended owner | Why |
|---|---|---|
| Barcode and SKU | POS | Goods are received in the shop, the scanner is in the shop |
| Short name | POS | Cashiers need a name they recognize |
| Shop price | POS | The price printed on the shop receipt |
| Website price | POS, or a separate field on the website | Depends on whether the prices are identical (see below) |
| Stock | POS | Physical sales happen there |
| Cost price and minimum price | POS only | Never leaves the POS |
| Photos, description, Google title | Website | Written for the online buyer, not for the cashier |
| Categories and menu on the website | Website | The website's structure is different from the structure of the shelves |
Yours may look different. A shop whose sales are mostly on the website, for example, can decide that the website owns the price. What matters is that the decision is written down, and that the developer builds the integration according to it.
Sync direction: who creates a new product
When new goods arrive, they have to appear in both systems. There are three ways to do it:
- Create in the POS, the website receives. You receive the goods in the shop, scan the barcode, set a price. The product appears on the website as a draft, and someone adds a photo and description before publishing. This is the common way in shops where most sales happen in-store.
- Create on the website, the POS receives. Fits a business that starts online and opens a shop. The problem: whoever creates a product on the website doesn't always enter a barcode, and without a barcode the cashier can't scan.
- Create in both, and the integration only updates price and stock. Sounds the safest, but it's the easiest way to create duplicates. Every product is created twice, by hand, and someone has to remember to link the two.
Why "two-way" is riskier than it sounds
Full two-way sync, where every change on either side passes to the other, sounds like the best solution. In practice it creates two problems:
- Collision. A shop employee changed a price to ₪44.90, and at the same hour someone on the website changed it to ₪42.90. Which price stays? Usually the one saved last, and that isn't necessarily the right one.
- Ping-pong. The POS updates the website, the website detects a change and sends it back to the POS, and the POS sends it again. In an integration that wasn't built carefully this can run endlessly and overload both sides.
The solution: one direction per field. Price and stock flow from the POS to the website, photos and descriptions stay on the website, orders flow from the website to the POS.
Barcode and SKU: the key that links the systems
For the integration to know that "Blue ceramic cup 400" in the POS and "Large blue mug" on the website are the same product, you need a shared identifier. The name can't be the identifier: it changes, has typos, and is written differently in each system.
The right identifier is a barcode or SKU, at the variant level. A black shirt in size M needs its own identifier, separate from the same shirt in size L. How to build SKUs that don't collide, and when to keep the manufacturer's barcode: Barcodes for a small business: a catalog without duplicates.
Note that every platform matches products in a different way:
- WordPress with WooCommerce, the store plugin for WordPress: import matches existing products by internal ID or by SKU. If you don't tick "update existing products", rows with an SKU that already exists are simply skipped.
- Shopify: a file import matches products by the handle, meaning the product's part of the page URL, not by SKU or barcode. A product with a different handle will be created as a new product, even if the SKU is identical.
- Shopify, another trap: according to its import guide, changing option values (for example "M" to "Medium") deletes the variant IDs and creates new ones. An integration with the POS that relies on the old IDs will stop updating them.
So before you rename sizes or colors on a connected website, ask the developer what this does to the integration.
Where duplicates come from
| What happened | What you see | How to prevent it |
|---|---|---|
| A product was created by hand in both the POS and the website | Two products, split stock | Create only on one side (the owner) |
| A barcode was typed with a space or a missing zero | The integration finds no match and creates a new one | Scan, don't type |
| A supplier changed packaging and barcode | A "new" product that is really the old one | Check before creating, update the barcode on the existing product |
| Variants are named differently in each system | Size M doesn't update | Identical size and color names, or match by SKU only |
First import: connecting a catalog that already exists
Most businesses don't start from zero. You have a POS with 600 products and a website with 350, some overlapping, some not. The first connection is the stage where most duplicates are created. This is how to do it carefully:
- Export both catalogs to a file. From the POS and from the website, with barcode, SKU, name, price and stock for each variant.
- Match by barcode. In one spreadsheet, join rows with the same barcode. Three lists come out: products that exist in both, products only in the POS, and products only on the website.
- Handle the "website only" list. These are usually products without a barcode, or with a barcode that was typed differently. Fix them by hand before connecting.
- Decide what to do with "POS only". Not everything sold in the shop needs to be on the website: bags, services, loose items. Mark them "not for the website".
- Test on 20 products. Connect a small group, including a product with sizes and colors, and check price, stock and name on both sides.
- Only then connect everything else. And keep the export files from day one, in case you need to go back.
Do you have a WordPress site that doesn't sell yet? Install WooCommerce from the plugins menu, and import the catalog from the POS into it as a CSV file, with the built-in import tool. There are no duplicates to clean here, but everything else still applies: a barcode or SKU for every variant, and a test on 20 products first.
A few limits worth knowing before a large import:
| Platform | Relevant limit |
|---|---|
| Wix | Up to 50,000 products, up to 6 options per product (size, color, etc.), up to 100 values per option, up to 1,000 variants per product |
| Shopify | Up to 2,048 variants per product (since October 2025; before that 100) |
| WordPress with WooCommerce | Images in an import are loaded from a URL only if your server manages to download them. Upload any failed image by hand |
Photos, descriptions and fields that exist only in the online store
The POS needs a short name, a price and a barcode. The website needs much more: several photos, a description, a size chart, materials, washing instructions, a Google title and description, related products. These fields exist only on the website, and that's fine.
The problem starts when the integration doesn't know they belong to the website. A common scenario: you update a price in the POS, the integration sends the website the whole product again, including an empty name and description, and overwrites what you wrote on the website. So:
- Ask the developer to make the integration update only specific fields. A price update changes price. A stock update changes stock. Nothing else.
- Separate the POS name from the website name. "Blue cup 400" in the POS, "Handmade blue ceramic mug, 400 ml" on the website. Both are right, each for its own reader.
- A new product from the POS goes to the website as a draft. This way no product is published without a photo and description.
A different price on the sales website and in the shop
There are good reasons for a different price: the website has shipping and packaging costs, or you want to compete on price online. There are also good reasons not to: customers compare, and the gap creates questions at the counter.
If you choose a different price, three things matter:
- Two price fields, not a "fixed discount". In the POS you keep a shop price and a website price, and the integration sends the website only the website price. A calculation like "website price = shop price minus 5%" breaks the first time someone rounds by hand.
- The displayed price is binding. According to the Consumer Protection Authority (הרשות להגנת הצרכן), the binding price is the price displayed on the product, even if the POS has a higher one. Charging above the displayed price is one of the violations for which a customer can claim statutory damages (פיצוי לדוגמה) of up to ₪10,000, without proving harm. So an old price forgotten on the website is a risk, not a technical detail.
- Decide in advance what to say at the counter. A customer shows a lower price on the website on her phone. Do you honor it in the shop? Write the policy, explain it to employees, and show it on the website. An argument at the counter is the most expensive way to find out you didn't decide. How to fix a gap between a displayed price and the register price: Shelf price differs from the register price.
Promotions in one channel only
A promotion isn't a price. "1+1 on socks" in the shop, or a newsletter coupon code on the website, are rules that apply at purchase time. If the integration doesn't distinguish between them, mistakes happen:
- A shop promotion is sent to the website as a new price. You marked it down in the POS to ₪29.90 for the weekend, and the website kept selling at this price for two more weeks because nobody changed it back.
- A website coupon that doesn't work in the shop. A customer arrives with a code from an email. The employee doesn't know what to do, and improvises a manual discount.
- A double promotion. A website discount on a price that was already marked down in the POS.
The rule: the base price flows between the systems. Promotions are defined in each channel separately, in its own promotions tool, with a start and end date. If you want a shared promotion, define it twice, on the same dates, and check both sides on the first day.
VAT: included or not
In Israel a consumer price is displayed including VAT. The Consumer Protection Authority writes that the law requires displaying only a total price, which includes VAT among other things, in Israeli currency. The VAT rate today is 18%.
The problem in an integration: not every system stores a price the same way. Some POS systems store a price before VAT and add it on the receipt, and some store the consumer price. Websites also have a setting: in WooCommerce it's called Prices entered with tax, and Shopify has a tax-inclusive pricing setting.
When the settings don't match, it looks like this:
| What happened | Price in the POS | What the website shows |
|---|---|---|
| The POS sends a price including VAT, the website thinks it's before VAT | ₪118 | ₪139.24 |
| The POS sends a price before VAT, the website thinks it includes VAT | ₪118 (₪100 before VAT) | ₪100 |
| The POS sends a rounded price before VAT, the website adds 18% | ₪19.90 (₪16.86 before VAT) | ₪19.89 |
The last row is the most annoying: a one-agora difference that appears only on some products, and makes customers think the prices are inconsistent. The simple solution: the integration passes the consumer price, including VAT, exactly as printed on the shelf, and the website is set to prices including VAT. This way what the customer sees on the website matches what she sees in the shop, down to the agora.
Cost price doesn't leave the POS
The POS holds information that shouldn't be on the website: cost price, the minimum price you're allowed to sell at, supplier, and employee details. When you connect a POS to a website, it's easy to forget that any information that passes to the website can reach other places: a plugin you installed, the company that maintains the website, an export file someone sent by email.
So:
- The integration receives only what it needs. The website's access key can read products, prices and stock. Not costs, not suppliers, not employees.
- A separate key for each system. The website, the accounting software and the mailing tool each get their own key. If one of them leaks, you revoke only that one.
- Check what passes. Ask the developer for an example of a product as the website receives it, and check with your own eyes that there is no cost price in it.
In KupaLi, for example, cost prices, minimum prices and employee details never leave the POS.
A product taken off the shelf
A product you stopped selling isn't deleted, either in the POS or on the website.
In the POS mark it inactive. Deleting can break sales reports for previous months, and a customer who returns the product next week needs the POS to recognize it.
On the website there are three options:
- Temporarily out of stock: leave the page with "Out of stock". In the structured data that Google reads there is a special value for this (OutOfStock).
- Discontinued, with a replacement: redirect the old address to the page of the new product, so customers and old links don't land on an empty page.
- Discontinued, with no replacement: you can mark it "discontinued" (this too has a value, Discontinued), or return a 404 error. According to Google, a page that returns 404 or 410 drops out of the index. An empty page that returns "OK" may appear in Search Console as a soft 404 error.
The decision should be part of the integration: when a product is marked inactive in the POS, what happens to its page on the website? If you don't define it, an integration may simply delete the product from the website, including the photos and description you wrote. Ask the developer what happens in your case.
Catalog checklist before you connect
- I wrote down the owner of each field: POS or website.
- I decided where a new product is created, and that it goes to the website as a draft.
- Every variant has a barcode or SKU, with no duplicates.
- I exported both catalogs, matched by barcode and handled "website only" and "POS only".
- I marked what doesn't go to the website: bags, services, loose items.
- I decided whether the website price is identical or different, and if different, it has its own field.
- I wrote down what to say at the counter when the website price is lower.
- Promotions are defined in each channel separately, with end dates.
- The integration passes a price including VAT, and the website is set to prices including VAT.
- I checked a product as the website receives it, and there is no cost price in it.
- I defined what happens on the website when a product is marked inactive in the POS.
- I tested on 20 products before connecting everything else.
How it works in KupaLi
In KupaLi you manage products in the POS, and the sales website receives them through the KupaLi API, even when it's built on WordPress, with the price, photo, sizes and colors. A price change in the POS reaches the website within about 5 seconds. Each system has its own key with permissions only for what it needs, and you revoke a key with one click.
Promotions and advanced stock management are included in the Smart POS plan, ₪119 per branch per month + VAT, with no setup fee and no commitment. Want to create products on the website and have them reach the POS, or a separate website price? That can be connected too, according to what the business needs.
Want to see how it works? Start 14 days free, no credit card. The full picture of connecting a POS to a website is in the complete buying guide. For stock, reservation and sizes read One stock for the shop and the website, and before talking to a vendor, go through the questions to ask a POS company.
This information was checked in November 2026 and is general, not legal or accounting advice. Website platform settings change; before connecting, check the settings on your site with your developer, and tax questions with 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?
Where is it better to manage products, in the POS or on the website?
For most businesses that sell mainly in-store: barcode, price and stock in the POS, and photos and descriptions on the website. What matters is that each field has one owner, in writing.
How do you prevent duplicates when connecting a POS to an online store?
Match products by barcode or SKU at the variant level, never by name. Create a new product in one system only, and the other receives it through the integration.
What should I watch for when the website price differs from the shop price?
Every price shown to a customer must include VAT, and according to the Consumer Protection Authority the price displayed on the product is binding, even if the POS has a higher one. Decide in advance what to tell a customer who shows a website price in the shop. For a specific legal question, consult a lawyer.
Why is the website price off by one agora from the shop price?
Probably the POS sends a rounded price before VAT, and the website adds 18%. Send the website the consumer price including VAT, and set the website to prices including VAT.
What do I do in the online store with a product we stopped selling?
If there is a replacement, redirect the address to its page. If not, mark "discontinued" or return 404. In the POS, don't delete it; mark it inactive.