Before White Friday: nine back-office checks
Nine checks in five phases before White Friday, expected on 27 November 2026: stock per location, tax, coupons, returns, and who watches failed syncs.
White Friday deals usually start before the Friday itself, and the back office feels them after. A product sold with no stock behind it, or last year’s coupon still switched on, turns up in your ERP days after the sale ends.
The prep breaks down into nine checks on stock, orders and the books, in five phases, from four weeks out to after the sale.
When White Friday falls in 2026
White Friday is the name used in the Gulf and the wider Arab world for Black Friday: the Friday after US Thanksgiving. Thanksgiving 2026 is Thursday 26 November, so White Friday is expected on Friday 27 November 2026. How long your deals run before and after that day is up to you.
Before you start
It helps to have four lists ready:
- The products in the sale, with the SKU of each product and each variant.
- Your store’s locations in Zid, and the ERP warehouse that matches each one.
- Your current coupons in Zid, with each one’s end date.
- The name of the person who watches orders during sale week.
Nine checks in five phases
Four weeks out
Checks 1 to 3: product codes, tax settings, shipping methods and fees.
Two weeks out
Checks 4 and 5: stock per location, coupon review.
Sale week
Checks 6 and 7: the returns path, and a test order from payment to the ERP.
The Friday
Check 8: one named person watches orders that fail to sync.
After the sale
Check 9: reconcile orders, returns and stock, then read the numbers.
1. Product codes
It helps if every product in the sale has a matching ERP record under the same code. If you add a product to Zid shortly before the sale, create its record in the ERP at the same time. For products with variants, such as size and color, check the code of each variant.
2. Tax settings
Zid calculates the tax on an order from your store’s tax settings. The check is whether those settings line up with the tax codes in your ERP, especially for products with a different rate or an exemption. Leave the settings alone during sale week. These are points to check only. Confirm the right tax treatment with your accountant.
3. Shipping methods and fees
Free shipping or reduced fees change the shipping amount on the order. Check your shipping methods and fees in Zid before the sale, and open a past order in your ERP to see how shipping shows up there.
4. Stock per location
Selling stock you do not have ends in an order you cannot ship on time. Compare the quantity at each Zid location with the matching ERP warehouse, starting with your best sellers. If your ERP is the source of stock, fix any gap in the ERP itself.
5. Coupon review
List the coupons that are active in Zid and check each one’s end date and usage limit. Switch off any old coupon that is not part of the sale. Create the sale coupons a few days ahead, each with a set start date and end date.
6. The returns path
Most sale returns arrive after the sale is over. Settle three things beforehand: the return policy on sale items, who approves a return in Zid, and how a return is recorded in the ERP. One rule makes reconciling easier later: one credit note per return.
7. A test order to the ERP
A few days before the sale, place a test order on a sale product, with the sale coupon and one of the sale shipping methods. Then check the order in the ERP: customer, items, tax, shipping and discount. If your ERP is Odoo, ERPNext or Wafeq, return it, and check the credit note in the ERP too.
8. Watching failed syncs
On the day, one named person watches orders that fail to sync to the ERP and decides what happens to them. Set review times through the day, such as the start, middle and end of the shift, and who to call when needed.
9. Reconcile after the sale
A few days after the sale, match the orders in Zid against the ERP for the same period, returns against credit notes, and stock at each location against its warehouse. Then read the sale’s numbers: sales, customers and products. They help you plan stock for the next season.
The checklist
| Check | Why | When |
|---|---|---|
| 1. Product codes | Every Zid product has a matching ERP record | Four weeks out |
| 2. Tax settings | Order tax matches the ERP’s tax codes | Four weeks out |
| 3. Shipping methods and fees | Shipping deals change the shipping amount | Four weeks out |
| 4. Stock per location | Nothing sells without stock behind it | Two weeks out |
| 5. Coupon review | No old coupon stays switched on | Two weeks out |
| 6. Returns path | Returns arrive after the sale | Sale week |
| 7. Test order | Order, discount and return checked in the ERP | Sale week |
| 8. Watching failed syncs | No failed order goes unwatched | The Friday |
| 9. Reconcile | The books match what sold and what came back | After the sale |
Where the app fits
Zid Integrations connects your Zid store to your ERP or accounting app, and ties into several of these checks:
- Orders (checks 7 and 9): every paid order is written into your ERP with the customer, items, tax and shipping, then read back to confirm it is there. The same order never posts twice.
- Returns (check 6): with Odoo, ERPNext and Wafeq, each return posts to your ERP as one credit note.
- Stock (check 4): stock flows from your ERP warehouses to each Zid location and is read back to confirm. Stock starts on the Growth plan; details of each plan are on the app’s page.
- Coupons and failed syncs (checks 5 and 8): once you approve, the assistant in the app can create a coupon, add wallet credit for up to 50 shoppers per run, change an order status or retry a failed sync. The app creates, updates and deactivates coupons, and never deletes them.
- The sale’s numbers (check 9): the insights dashboard is on by default at install, with an overview plus sales, customers and products, including Revenue, Orders and Average order, refreshed every night.
Our team does the setup with you, and you go live about two weeks after install, once you approve the test report. Posting orders and returns starts on the Starter plan; details of each plan and its price are on the app’s page in the Zid App Market.
Questions merchants ask
What if an order fails to sync on the Friday?
The assistant in the app can retry the sync once you approve. A retry does not create a duplicate order in the ERP.
How do sale returns show up in the ERP?
With Odoo, ERPNext and Wafeq, each return posts as one credit note, so each return is easy to match to its credit note.
How soon do you go live after installing?
In about two weeks, after the connection is tested on your store’s orders and you approve the test report.
To have your sale orders and returns posted to your ERP, install the app from the Zid App Market.
