Customers, Orders and Returns: Shop and Website in One Picture
Shop and online store? One customer record, web-order returns in store, who issues the receipt, what your accountant needs, plus Amendment 13 and the spam law.
Written with AI assistance and fact-checked against sources
A customer bought a pair of jeans from your online store on Sunday. On Tuesday she walks into the shop to return them. In the POS she has no customer record, the order doesn't appear, and the employee gives her ₪250 in cash from the drawer. The website still thinks the jeans sold, the stock didn't go back, the charge on her credit card stays, and at the end of the month your accountant sees a sale with no return and a drawer that's short ₪250.
All of this happens when the shop and the sales website are connected on stock and products, but not on customers and orders. This guide covers that part: how to tell it's the same customer, how to manage points, gift cards and returns between channels, who issues the receipt for a website order, what to send your accountant, and what the Privacy Protection Law and the anti-spam law require when you merge your customer list.
In short
- Identify a customer by mobile number, in the shop and on the website. Email is a secondary identifier.
- Every payment gets one receipt, from the system that collected it. If the website collected the payment, the POS records the sale for stock and reports, with no additional document.
- Cancelling an online order: up to 14 days from receiving the product, a refund within 14 days, a cancellation fee of up to 5% or ₪100 (whichever is lower). A customer can also cancel verbally in the shop.
- Points, gift cards and credit vouchers are managed as one balance for both channels, otherwise they will be redeemed twice.
- Amendment 13 to the Privacy Protection Law has been in force since August 14, 2025. Advertising without consent can cost up to ₪1,000 in compensation per message.
One customer in two channels: how to know it's the same person
In the shop you ask the customer for a phone number. On the website she registers with an email, and sometimes a phone too. Without a clear rule you'll get two records for the same customer, and each sees half the picture: the points in the POS, the orders on the website.
What works in small businesses:
- Primary identifier: mobile number. Almost every customer is willing to give it at the register, and you can ask for it at website checkout too. Make the phone field on the website mandatory.
- Secondary identifier: email. Good for receipts and shipping updates, but people change emails and mistype them.
- One format. 050-1234567, 0501234567 and 972501234567 are the same number. Make sure the integration stores them all in one format, otherwise each variation opens a new record.
- Name is not an identifier. Two "Michal Cohen"s are not necessarily the same Michal. Don't merge records by name alone.
When duplicates already exist: merge when the mobile number matches. When only the email matches, ask the customer at the next visit. Before any merge, check three balances that must not get lost: points, gift card, and consent to marketing. A customer who asked to be removed from marketing on one record stays out of marketing after the merge too.
How it looks in practice, field by field:
| Field | In the shop | On the website | Where to manage it |
|---|---|---|---|
| Mobile number | Collected | Collected (mandatory) | The shared identifier, in both systems |
| Sometimes | Collected | On the website | |
| Shipping address | Not needed | Collected | On the website only |
| Points, gift card, vouchers | Earned and redeemed | Earned and redeemed | In one system only |
| Consent to marketing | Collected | Collected | One status that updates in both directions |
| Purchase history | Recorded | Recorded | In both, and merged into one report |
Which system is the "source" for each type of data, and what that means for the whole integration: the guide POS with website integration. Matching products and barcodes between the POS and the website: Products and prices in the POS and on the website.
Points, gift cards and vouchers: one balance, not two
Every balance has one home. If points are stored both in the POS and on the website, a customer can redeem the same 200 points twice, once in each channel. The same with a ₪300 gift card.
- Loyalty points. The other system asks for the balance at the moment of redemption and deducts it immediately. On the website, deduct when the payment goes through and give them back if the order is cancelled.
- Gift card. One code, one balance, partial redemption. A gift card bought on the website needs to work in the shop, and vice versa. If you limit the validity of a purchase voucher (תו קנייה), the law requires at least five years from the date of issue, and both dates must appear on it.
- Credit voucher (שובר זיכוי). Valid for at least two years, for the amount paid in the transaction, and under the law a condition limiting its redemption has no validity. So the simplest option: one voucher that works in the shop and on the website.
- Returning a product that earned points. Decide in advance: the points earned on it are deducted, and the points the customer redeemed in the purchase go back to her. Otherwise every return starts an argument.
The differences between a credit voucher, a purchase voucher and a gift voucher, and the validity of each, are in the guide Credit voucher validity. And if you don't have a loyalty club yet, start with A loyalty club for a small business.
Returning an online order in the shop
A purchase on a website is a "distance sale transaction" (עסקת מכר מרחוק) under section 14C of the Consumer Protection Law. These are the rules the employee at the counter needs to know:
- The cancellation window. From the day of purchase until 14 days from the day the customer received the product, or the document with the transaction details, whichever is later.
- Four months for certain customers. A senior citizen (65 and over), a person with a disability and a new immigrant (up to five years from immigration) can cancel within four months, if the order involved a conversation with the business, including a conversation "by electronic communication".
- Cancellation fee. When the customer simply changed her mind: up to 5% of the price or ₪100, whichever is lower. When the product is defective, didn't match the description or didn't arrive on time: no cancellation fee at all.
- A refund within 14 days of receiving the cancellation notice. You cancel the charge and give the customer a copy of the cancellation notice.
- A cancellation notice can also be given orally, by phone or at the business premises, and also by email and online. The website must have a prominent cancellation link on the main page, and the ways to cancel must also appear on the invoice or receipt.
- Exceptions. These rules don't apply, for example, to perishable products and products made especially for the customer.
And what about a credit voucher instead of money? Under section 14G, a credit voucher is given when the customer has no right to a refund by law. Within the cancellation window of a website order, she has such a right. You can offer a voucher, but not force it.
At the counter, step by step
- Find the order by mobile number or order number. If the POS doesn't see website orders, this is the first connection to set up.
- Check the receipt date and the condition of the product.
- Refund the money the same way it was paid. An order paid by card on the website is refunded through the website's payment system, where the charge sits. Cash from the drawer doesn't cancel the charge, and leaves the POS short.
- A credit document that refers to the original invoice. The bookkeeping regulations require that a credit notice include the numbers and dates of the invoices it refers to. So the credit is issued by the system that issued the original document, usually the website's invoicing system.
- Return to stock of the branch that received the product. How this works with several branches: One stock for the shop and the website.
- Update the order on the website to "returned", so the customer doesn't get a "How was the product?" email.
| The case | How the money returns | Who issues the credit document | Stock |
|---|---|---|---|
| Paid by card on the website, returned in the shop | Cancelling the charge in the website's payment system | The website's invoicing system | Returns to the branch that received it |
| Ordered on the website, paid at pickup in the shop | In the POS, by the same payment method | The POS | Returns to the branch that received it |
| Paid through a payment link the shop sent | Through the system that created the link | The system that collected and issued the receipt | Returns to the branch that received it |
| Bought in the shop, the customer wants to return it by post | Per the shop's return policy, by the same payment method | The POS | Returns when the product arrives |
Who issues the receipt for an order from the sales website
The rule: whoever received the money issues the document. Once.
The Income Tax (Bookkeeping) Regulations provide that a receipt "shall be made out for each payment separately", and that a copy is given to the payer. One payment, one receipt. In practice there are three situations:
- The customer paid on the website. The website, or the invoicing system connected to it, issues the document and sends it. The POS only records that the item sold and at what price, for stock and reports.
- The customer ordered on the website and paid at pickup. The POS collects and issues the receipt, as with any shop sale. The website marks the order as "paid".
- You sent the customer a payment link. The document comes from the system that created the link and collected the money.
Why not twice? Two documents for the same sale record the income and the VAT twice in the books. Your accountant will have to cancel one of them with a credit document, and the customer holds two receipts for one purchase. This failure is easy to prevent: decide in advance which system issues documents in each of the three situations.
Two more things worth checking with the website's invoicing system:
- A receipt by email. You may send a receipt or invoice as a "computerized document" (מסמך ממוחשב), under the conditions of section 18B of the bookkeeping regulations: the words "computerized document" appear clearly, the customer agreed to receive computerized documents before the first document, and the consent is kept. Ask the invoicing system how it handles this.
- A business customer. If an authorized dealer (עוסק מורשה) places a website order of more than ₪5,000 before VAT, they need an allocation number (מספר הקצאה) on the tax invoice in order to deduct the VAT. This threshold has been in force since June 1, 2026; from January 1, 2026 until then it stood at ₪10,000. Make sure the website's invoicing system asks for an allocation number.
All sales in one report, and what to send your accountant
You need to see one number: how much did I sell today, in the shop and on the website, after returns. Your accountant needs to see the same number broken down into documents. The integration between the POS and the website should give both.
What to send your accountant each month:
- Register closing reports from the shop. If closing isn't organized yet, start with Closing the register at the end of the day.
- The list of documents the website issued: receipts, invoices and credit documents.
- The payout report from the website's payment provider, including fees and refunds.
- Settlement reports from the shop's card terminal.
- Gift cards: how much sold and how much redeemed, in each channel.
- Orders that were paid and not yet delivered at the end of the month.
Three five-minute checks, before you send:
- The number of orders paid on the website equals the number of receipts the website issued.
- Total payouts from the payment provider equal the total of receipts on the website, minus fees and refunds.
- No website order also appears as a document in the POS.
If one of the checks doesn't add up, you'll find the problem now, not in the annual report.
Privacy: what Amendment 13 changes when you merge customers
Amendment 13 to the Privacy Protection Law was approved by the Knesset on August 5, 2024 and came into force on August 14, 2025. The Privacy Protection Authority describes it as the most comprehensive update to privacy law in Israel since the law was enacted, and it gave the Authority the power to impose financial sanctions. When you connect the shop's customer list to the website's, you're building one larger database. What this means in practice:
- Database registration: mostly no longer required. After the amendment, the registration duty applies mainly to public bodies and to a database whose main purpose is collecting information in order to pass it to others, with more than 10,000 people. An ordinary shop doesn't fall into these. The other duties do apply to it.
- Notice when collecting information (section 11). When you ask a customer for details, you need to tell her: whether she's obliged to provide them or it's up to her, and what happens if she refuses; why they're required; who the business is and how to contact it; to whom they will be given and why; and that she has the right to inspect them and ask to correct them. A court can award compensation of up to ₪10,000 without proof of harm if a customer asked for the notice and didn't receive it within 30 days. On the website it's a line next to the payment fields. In the shop, a short sign next to the register with a link to the policy.
- Use only for the stated purpose. Information in a database is processed only for its defined purpose. A phone number given for delivery is not permission to send promotions.
- An agreement with whoever touches the information. The website platform, a developer who built the integration, the mailing company: under the information security regulations, the agreement with an external party that gets access to the database must set what information it processes and for what purpose, which systems it accesses, for how long, and what happens to the information at the end of the engagement.
- Permissions by role. Every employee, and every connected system, accesses only what their role requires. How to set this up in the POS: Employee permissions in the POS.
- Requests to inspect and correct. A customer may inspect the information you hold on her and ask to correct or delete incorrect information. With two systems, the correction has to reach both.
What to keep and what to delete in the customer list, and how to run a 20-minute check: Customer data in a small business.
Consent to marketing when you have two channels
Section 30A of the Communications Law, the "spam law", prohibits sending an advertisement by SMS, email, fax or automatic dialing without the recipient's explicit prior consent, in writing, including in an electronic message or a recorded call. For an advertisement sent knowingly in violation of the law, a court can award compensation of up to ₪1,000 per message, without proof of harm. And the law presumes the sending was knowing, unless the business proves otherwise.
There is an exception for customers who bought from you. You may send them an advertisement without explicit consent only when all three conditions are met:
- The customer gave her details during a purchase or negotiations for a purchase, and you told her the details would be used to send advertising.
- You gave her an opportunity to refuse, and she didn't refuse.
- The advertisement is about products or services of a kind similar to what she bought.
What must appear in the message itself: in an email, the word "advertisement" (פרסומת) in the subject line, the business name, its address and contact details, and a valid address for sending an opt-out. In an SMS, the wording of the law requires only the business name and a way to contact the business to opt out. A customer may refuse at any time, in writing or in the same way she received the message, at no charge.
When you have a shop and a website, the danger isn't in the law but in the sync. A customer clicks "unsubscribe" in an email from the website, and a week later gets an SMS from the POS. Here's how to prevent it:
- One consent status per customer, updated in both directions before every send.
- Record how consent was given: date, channel, and the wording the customer saw.
- At website checkout, a separate checkbox, not pre-ticked. In the shop, one clear question.
- An opt-out applies to every channel the customer asked for, even if they sit in different systems.
How KupaLi connects to this
In KupaLi, website orders don't get a double receipt: the website collects and sends the receipt, and the POS updates stock and records what sold and at what price. Every sale, refund and new customer is sent to your systems (accounting, reports and mailing) through the API connection. Each connected system has its own key, with permissions only for what it needs, and you revoke a key with one click. Cost prices, minimum prices and employee details never leave the POS.
The Smart POS plan at ₪119 per branch per month + VAT includes a loyalty club, gift cards, marketing and an online store where customers pay at pickup or through a payment link that you send. No setup fee and no commitment.
Want customers who register on the website to appear in the POS too, points to be earned and redeemed in both channels, or the return of a website order to be closed in the shop? That can be connected too, according to what the business needs. Before you start, go through the questions to ask a POS company before connecting to a website.
Want to see how it works? Start 14 days free, no credit card.
This information was checked in November 2026 and is general. It is not legal or accounting advice; before deciding, check with a lawyer and an 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?
A customer bought from the online store and wants to return it in the physical shop. Do I have to accept?
In a cancellation that isn't due to a defect, the law provides that the customer returns the product to the business premises, and the cancellation notice can also be given orally at the business premises. If you have a shop, prepare to accept returns of website orders there.
Can I give a credit voucher instead of money for a website order?
Within the cancellation window, you can offer one but not force it. The customer is entitled to a refund within 14 days of the cancellation notice, less a cancellation fee of up to 5% or ₪100 (whichever is lower). A credit voucher is given when the customer has no right to a refund.
Who issues a receipt when the customer orders on the website and pays at pickup?
The POS, at the moment of payment, as with any shop sale. The website only marks the order as paid and doesn't issue a document of its own.
Do I need to register my customer database with the Privacy Protection Authority?
Usually not. After Amendment 13, the registration duty applies mainly to public bodies and to databases whose main purpose is passing information to others, with more than 10,000 people. The duties of notice to the customer, information security and the right of inspection apply to every business.
May I send an SMS to a customer who bought from me?
Only if she agreed in advance, or if at the time of purchase you told her her details would be used for advertising, gave her the chance to refuse and she didn't, and the message is about similar products. In every message state the business name and a simple way to opt out.