Questions to Ask a POS Company Before Connecting to Your Website
26 questions for a POS company before connecting to your website (WordPress, Shopify, Wix): sync, faults, receipts, security, costs, exit. With red flags.
Written with AI assistance and fact-checked against sources
Every POS company will tell you it has "website integration". The difference shows up a month later: when the last item sells twice, when the website stops updating and nobody notices, or when it turns out the plugin was written three years ago and there's nobody to fix it. You can find all this out in a single sales call, if you ask the right questions.
We've collected 26 questions in seven groups, in the order to ask them. For each question we wrote what a good answer sounds like and what should raise a red flag. At the end there's a short printable checklist. It's worth bringing your developer or website builder to the call too, because some of the questions are for them.
In short
- Ask what exactly passes between the POS and the sales website, in which direction, and which system is the source for each piece of data.
- Ask how long until a shop sale reaches the online store, and whether the item is held for the customer during payment. "At night" or "every quarter of an hour" is a weak answer for a business with low stock.
- Ask what happens when something breaks: who gets an alert, who fixes it, and what happens to sales when the internet in the shop goes down.
- Ask who issues the receipt for a website order. The right answer: one system only.
- Ask for all costs in writing, and make sure you can leave with your data.
Before the call: three things to prepare
- What your website is built on: WordPress with WooCommerce, Shopify, Wix, a custom-built site, or a WordPress site that doesn't sell yet. The answers change by platform.
- What you want to connect: only stock? Products and prices too? Customers and loyalty too? Write it in one line for each type of data.
- How many products, sizes and colors you have: a shop with 200 styles, 4 sizes and 3 colors manages 2,400 separate items. This changes the answers.
If you haven't yet chosen how to connect, start with the complete guide to a POS with website integration.
1. What connects, and where to
| Question | A good answer sounds like | Red flag |
|---|---|---|
| 1. Which online store platforms do you support, and how? And what if our WordPress site doesn't have a store yet? | "WordPress with WooCommerce through a plugin, a custom site through the API. For a WordPress site that doesn't sell: add WooCommerce, or connect it directly to the API. Here's a customer who works this way." | "Everything is supported", without explaining how |
| 2. What exactly passes, and in which direction? | A list: stock in both directions, products and prices from the POS to the website, orders from the website to the POS | "Everything syncs" |
| 3. Which system is the source for each type of data? What happens when I change a price on the website? | A clear answer for each field, and a rule for what happens when it's changed on the other side | "You can change it in both places", with no rule |
| 4. How do you match products between the POS and the website the first time? | By barcode or SKU, with a list of what wasn't matched before the import | By product name |
Why question 3 matters: when two systems can change the same field, they overwrite each other. We wrote about the choice of what to manage where in the guide on products and prices.
And about question 1: WooCommerce is the store plugin for WordPress. Do you have a WordPress site without a store? You install WooCommerce from the plugins menu, and from there it connects to the POS like any WooCommerce store.
2. Speed and reservation
| Question | A good answer sounds like | Red flag |
|---|---|---|
| 5. How long until a shop sale reaches the website? | "Within seconds. The POS sends an update the moment there's a sale." | "On a nightly sync" or "every quarter of an hour" |
| 6. Is the item held for the customer while she pays on the website? For how long? | "Yes, for a few minutes, and it can be changed." | "No need, it doesn't happen" |
| 7. What happens if the item sells in the shop just as the customer pays on the website? | "The website gets a notification and can contact the customer." | No answer, or "the customer will get an automatic cancellation email" without you knowing |
| 8. Can I hide the last units on the website (a safety margin)? | "Yes, per product or category." | "No, the website always shows all the stock" |
Two numbers that help with questions 5 and 6. In sync tools like Zapier, most triggers check for something new every 15 minutes on the free plan and every 2 minutes on the Professional plan. When one item is left, a quarter of an hour is a long time. At the other extreme, WooCommerce by default holds stock for an unpaid order for 60 minutes, and only then cancels it. A good reservation should be long enough to finish a payment, and short enough not to block the shelf. For example, with the KupaLi API the item is held for the customer for 10 minutes, and you can change that.
We went into more detail on stock, sizes, returns and multiple branches in the guide on shared stock for the shop and the website.
3. The technical side: questions for the developer
| Question | A good answer sounds like | Red flag |
|---|---|---|
| 9. Is there API documentation the developer can read? | "Yes, a full guide with examples." | "We'll send it after you sign", without at least a summary |
| 10. Can I test the integration without touching real stock? | A clear explanation of how to test before going live | "Test on the live website" |
| 11. If there's a ready plugin: who wrote it, who maintains it, and when was it last updated? | "We did, and it's updated when the platform changes." | "A freelancer wrote it once" |
| 12. Is there a limit on the number of updates or calls? | A clear number, and what happens when you reach it | "We have no idea" |
Why question 11 matters: platforms change the rules. In Shopify, the old REST interface became "legacy" on October 1, 2024, and from April 1, 2025 every new public app must be built on the GraphQL interface. A plugin nobody maintains can stop working without you touching anything.
4. When something breaks
| Question | A good answer sounds like | Red flag |
|---|---|---|
| 13. What happens when the website is unavailable to receive an update? And if the same update arrives twice? | "We retry, no sale is lost, and a duplicate update is detected and not counted twice." | "The update just won't arrive" |
| 14. How will I know the integration stopped working? | "There's an alert, and a log you can check." | "You'll notice when stock doesn't add up" |
| 15. What happens when the internet in the shop goes down? | "The POS keeps selling, and everything reaches the website when the connection returns." | "The POS doesn't work without internet" |
| 16. Who handles a fault: you, the developer or both? | A written split of responsibilities and a response time | "It depends", without anyone's name |
Why questions 13 and 14 matter: an integration doesn't always break loudly. In WooCommerce, after 5 consecutive delivery failures, the notifications the website sends out are disabled. 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. Without an alert, you'll only find out in a stock count.
We wrote separately about the moment the internet goes down: Online or offline POS: what happens when the internet goes down?
5. Receipts and money
| Question | A good answer sounds like | Red flag |
|---|---|---|
| 17. Who issues the receipt for a website order? | "One system only, the one that charged the customer. The other only records the sale." | "Both", or "not sure" |
| 18. Is the software registered in the Israel Tax Authority's Software Registry (מרשם התוכנות) and does it produce a uniform-format file (קובץ במבנה אחיד)? | "Yes, and here's how to produce it." | "No need" |
| 19. Do credit card numbers pass through the POS or through the integration? | "No. Payment on the website is made on the payment provider's page." | "Yes, we store them for you" |
Why: according to Kol Zchut, a business owner must issue a receipt immediately upon receiving payment. Two systems issuing a receipt for the same sale create a mess in the books. And about cards: 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. On software registration: the Tax Authority requires registering accounting software that is sold or rented to others, and registration requires producing files in a uniform format. More on receipts, returns and what goes to your accountant in the guide on customers and orders.
6. Security and privacy
| Question | A good answer sounds like | Red flag |
|---|---|---|
| 20. How does the website connect to the POS? | "A separate key for each system, with permissions only for what it needs. Revoked with one click." | "Give the developer your username and password" |
| 21. Are the updates the POS sends to the website signed? | "Yes, the website can verify the update really came from the POS." | "What do you mean, signed?" |
| 22. What data never leaves the POS? | "Cost prices, minimum prices and employee details." | "The API sees everything" |
| 23. Where is the data stored, and who at your company can see customer details? | A clear location and an answer to who accesses it and why | "In the cloud", with no details |
A separate key with limited permissions is standard, not a luxury. In WooCommerce you set each key to read, write or read/write, and in Wix you give the key only the permissions it needs. The notifications WooCommerce and Shopify send are also signed. If a POS vendor doesn't meet the same level, that's an answer. And customer details are also a legal matter: Amendment 13 to the Privacy Protection Law came into force on August 14, 2025, and gave the Privacy Protection Authority the power to impose financial sanctions.
7. Costs, data ownership and support
| Question | A good answer sounds like | Red flag |
|---|---|---|
| 24. What does it really cost: setup, monthly, and by usage? | All lines in writing, once they understand what you want to connect | "It depends", even after you explained |
| 25. If I leave, how do I get my products, customers and sales out? | "You export on your own, in regular files, free of charge." | "We'll export it for you, for a fee" or "you can't" |
| 26. Who answers the developer when they're stuck, and how fast? | A technical support channel and a response time in writing | "Contact a sales representative" |
And three more lines worth asking for in the quote: how much a change or addition costs later, who pays when the website platform changes version, and whether there's a minimum contract period.
Three answers that mean it's time to find another vendor
- "We don't know what happens when the integration goes down." Someone has to know, ideally whoever built it.
- "Give us the website password." An integration uses a limited key that can be revoked, not with your password.
- "It's hard to get the data out." The data about your customers and sales is yours.
How KupaLi answers these questions
| Question | KupaLi's answer |
|---|---|
| Speed (5) | A sale, price change or stock update in the POS reaches the website within about 5 seconds |
| Reservation (6-7) | The item is held for the customer for 10 minutes (adjustable). If it still sells in the shop, the website gets a notification and can contact the customer |
| What passes (2) | Products with price, photo, sizes and colors. Sales, returns and new customers are sent to your systems |
| Platforms (1) | The API works with any programming language and any server, so a WordPress site can be connected too, with or without WooCommerce. The developer gets a full guide with examples |
| Internet down (15) | Offline mode on both plans: you keep selling with cash and cheques, and everything syncs when the connection returns |
| Receipts (17) | 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 |
| Security (20-22) | A key for each system with permissions only for what it needs, revoked with one click. Every update to the website is signed. Cost prices, minimum prices and employee details don't leave the POS |
| Data (23) | On servers in Israel, including backups |
| Export (25) | Reports for any period, data export and a uniform-format file are included on both plans |
| Price (24) | The POS: ₪79 or ₪119 per branch per month, before VAT, no setup fee and no commitment. The API: priced by what you connect |
Need something that isn't in the table, like products created on the website that flow to the POS, loyalty points in the shop and on the website, or in-store pickup? That can be connected too. We connect according to what the business needs. Tell us what you have today, and we'll come back with a quote. The full plans are on the pricing page, and more about the POS on the home page.
Checklist to print
- We know which platforms are supported, and how it connects to ours.
- There's a written list: what passes, in which direction, and which system is the source.
- Products are matched by barcode or SKU, not by name.
- A shop sale reaches the website within seconds.
- The item is held for the customer during payment, and we know for how long.
- It's clear what happens when the item sells in the shop in the middle of a website payment.
- You can hide the last units on the website.
- The developer read the API documentation.
- There's a way to test before going live.
- We know who maintains the plugin and when it was last updated.
- There's an alert when the integration goes down, and a log to check.
- The POS works without internet and syncs when it returns.
- There's a written split: who handles a fault and how fast.
- Only one system issues a receipt for a website order.
- Card numbers don't pass through the POS or the integration.
- A separate key for each system, with limited permissions.
- The updates are signed.
- Cost prices don't leave the POS.
- All costs in writing: setup, monthly, usage, changes.
- We can export all the data ourselves.
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 vendors change; before deciding, ask for answers in writing 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 the most important thing to ask a POS company before connecting to a sales website?
How long until a shop sale reaches the website, and whether the item is held for the customer during payment. These are the two questions that decide whether you'll sell the last item twice.
Should I bring a developer to the call with the POS company?
It's worth it. Questions about documentation, testing, limits and faults are for them, and they'll quickly hear whether the answers are serious.
What is a signed update, and why does it matter?
An update the POS sends to the website with a digital signature, so the website knows it really came from the POS. Without a signature, someone else can send the website a fake update.
What happens to sales when the internet in the shop goes down?
It depends on the POS. A POS with an offline mode keeps selling, and sends the sales through when the connection returns. Ask this explicitly.
Who issues a receipt when the customer buys on the website?
The system that charged the customer, usually the website or its invoicing system. The POS records the sale and lowers stock, with no second receipt.