Integrating Your Online Store with Your Accounting System: How Can You Manage Salla and Zid Sales and Inventory in One Place?
📅 19/11/2026
Integrating an online store with an accounting system aims to transfer order, product, inventory, and invoice data between the store and the accounting system according to clear rules. In Saudi Arabia, owners of Salla and Zid stores are looking for ways to reduce duplicate data entry and track sales from digital channels and physical branches. A cloud accounting system can bring this data together if the integration supports the required processes and handles exceptions, rather than merely transferring orders.
This guide focuses on the relationship between each store and the accounting system, not on connecting Salla and Zid directly to one another. It provides a practical plan for identifying data sources, synchronizing items, testing order and return workflows, and reviewing integration results before approval. All figures are hypothetical examples, and integration settings vary by platform, connector, and subscription plan.
Integrating an Online Store with an Accounting System: Why Is a Sales File Not Enough?
A sales file may show order values, but it does not answer questions about inventory, tax, and collections on its own. If you have an online store and a physical showroom, the last unit may be sold in the showroom while it still appears available online. A customer may request a refund after their invoice has already been included in a previous tax return. The accountant needs to know how each event affects accounts, the warehouse, and documents.
The benefits begin when the order is linked to its original identifier, the invoice to the order, the inventory movement to the correct item, and the collection to the payment reference. You can then review orders that have not been posted or have been posted twice. Integration does not mean that all data automatically synchronizes in both directions; some connectors transfer orders only, while others support product or inventory updates. Consult the Salla Help Center for integration apps to understand that connector options vary, and then verify the connector you will use.
Identifying the Data Source Before Connecting Salla and Zid
Identify an authoritative source for each type of data. The accounting system may be the reference for available quantities and costs, while the store may be the reference for marketing descriptions and product images. The online selling price may differ from the showroom price because of a special campaign. Do not allow both systems to modify the same field without a rule for resolving conflicts.
| Data | Suggested source | Review rule |
|---|---|---|
| Item code | Accounting system | Unique code for each variant |
| Product description and images | Store | Do not replace a marketing description without approval |
| Available inventory | Accounting system or inventory service | Deduct reservations according to policy |
| Order | Store | Stable channel and order identifier |
| Tax invoice | Designated issuing party | Avoid duplicate issuance |
| Collection | Payment provider and bank | Match transaction reference |
This table is a starting point, not a mandatory description of every integration. A business may need a separate order management system if it sells through several platforms. Review sales, inventory, and accounting integration to understand the relationship between operational and financial data.
Book a demo to review how the integration works with your store.
Preparing Product and Variant Codes Before Inventory Synchronization
Start with the SKU, the identifier a business uses to distinguish items and variants. If you sell a shirt in three colors and four sizes, you may need 12 different codes. Do not map all variants to one item unless the business actually treats them as a single inventory item. The commercial name alone is insufficient because a product may appear under a different title in each channel.
In a hypothetical example, a warehouse holds eight medium black shirts and three large black shirts. If both variants are mapped to the same code, 11 units will appear available without identifying the size. A customer may purchase a size that is unavailable. The solution is to create a mapping between the variant identifier in Salla or Zid and the internal code, unit of measure, and warehouse. Test the change on a limited number of products before synchronizing the entire catalog.
If a product is a bundle of two or more items, determine whether it is stocked as a ready-made composite item or assembled to order. In the second case, bundle availability may be limited by the least available component, taking the required quantities into account. Inventory management helps explain the difference between physical stock and stock available for sale.
When Does a Store Order Become an Invoice?
An order status does not always determine the moment of revenue recognition or invoice issuance. An order may be created before payment, a customer may pay in advance, or an order may be canceled before shipment. Identify an appropriate event for issuing documents according to the nature of the supply and tax obligations. Do not rely on one rule for every case without consulting the accountant.
Map a clear workflow: new order, payment or selection of cash on delivery, inventory reservation, preparation, shipping, delivery, cancellation or return. Link each status to the appropriate accounting and operational action. If the store already issues the tax invoice, the accounting system should transfer its data without issuing a second tax document for the same supply without reason. If the accounting system is the issuing party, the order confirmation should not become a separate tax invoice.
Review the electronic invoicing software and the VAT Implementing Regulations when determining issuance and correction timing. The treatment of advance payments may differ from the timing of accounting revenue recognition. Have the technical team test the rules defined by the accountant rather than assuming that order status alone is sufficient.
A Practical Example of a Paid Order and Inventory Synchronization
Suppose a store sells two units at SAR 115 each, including 15% VAT, and each unit costs SAR 60. The total is SAR 230, net revenue is SAR 200, and VAT is SAR 30. Assume the sale has taken place and the business is the principal seller. If the payment provider collects the amount on behalf of the store, the simplified entry is a debit to receivables from the payment provider of 230, a credit to sales of 200, and a credit to output VAT of 30. The cost entry is a debit to cost of sales of 120 and a credit to inventory of 120.
If inventory before the sale is 10 units, it becomes eight after the two units leave. If the business reserves stock when an order is placed and deducts it physically at shipment, however, physical stock may be 10 while available stock is eight before shipment. The system must not deduct the quantity once at reservation and again when the order status changes without releasing the reservation.
| Event | Inventory effect | Expected financial effect |
|---|---|---|
| New order | Reservation according to policy | No automatic revenue merely because an order exists |
| Advance payment | Reservation continues | Recognize collection and liability as appropriate |
| Delivery of sale | Two units leave inventory | Revenue and cost according to the applicable treatment |
| Payment settlement | No inventory movement | Clear the amount due from the provider and account for fees |
Test a hypothetical order workflow in the system before connecting production data.
Preventing Duplicate Orders During Integration
The store may resend an order notification if it does not receive a response from the connector, or an employee may press the manual posting button after a synchronization delay. If the system creates a new invoice every time, sales, tax, and inventory movements will be duplicated. The technical solution is to use a stable transaction key, such as the store identifier, order identifier, and event type, and check the record before creating a new document.
The order number alone is insufficient if you have two stores; order number 500 may exist in both Salla and Zid. Retain the channel and store identifiers. If the order status changes after posting, treat the change as an update or correction event according to the document status, not as a new sale. If synchronization fails, the reason, time, and order identifier should be visible, and reprocessing should be traceable.
The accounting workflow explains how a document flows into reports. Ask the provider to run a test that sends the same order twice and then resends the shipping status. The desired result is one sales document and a correct inventory movement, with a log showing that the duplicate did not create an additional transaction.
Managing Canceled Orders and Returns Between the Store and the System
When a customer cancels an order for which no tax document has been issued and no goods have left inventory, releasing the reservation and refunding the amount paid according to the appropriate treatment may be sufficient. If a tax document has been issued or the goods have been delivered, however, the cancellation or return must be handled according to the status of the supply and documents. Do not delete the original invoice merely because the order status has changed to canceled.
In the previous example, if the customer returns one unit worth SAR 115 and it is fit for sale, the simplified accounting effect may be a reduction in sales of 100 and VAT of 15, and a return to inventory worth 60 against a reduction in cost of sales. If the item is damaged, do not return it to stock available for sale without assessment. If the amount is refunded through the payment gateway, link the refund reference to the note and the order.
Test partial returns in particular, because some integrations transfer a full order cancellation without details of the returned line items. Determine whether discount, shipping, and tax information is transferred correctly. Refer to the sales system to identify the functions you need on the returns screen and in reports.
Salla Accounting Software and Zid Accounting Software: What Should You Verify?
When evaluating a Salla integration, start with the Salla partnership page and ask for an explanation of the functions available in the actual connector. When evaluating Zid, review the Zid partnership page and ask to verify the scope of the integration. Do not assume that the capabilities of the two platforms are identical or that the software subscription includes the connector cost. Check permission, subscription, and support requirements.
Ask about the direction of synchronization, the fields transferred, when updates occur, and how the connector handles product variants, warehouses, and previous orders. If you have more than one store, request a test connecting each store through a separate account or channel identifier according to the solution design. You should be able to distinguish sales from each channel in reports even if inventory is shared.
Explore the subscription plans and discuss the cost of connectors and additional channels.
A Daily Monitoring Dashboard for Connected Stores
Do not wait until month-end to discover that 40 orders never reached the accounting system. Create a daily report comparing the number of orders eligible for posting with the number of resulting documents, excluding cases that should not be posted. Include order values, the number of rejected or pending orders, the number of items without a matching code, and the oldest unresolved case.
| Metric | Daily example | Action |
|---|---|---|
| Eligible orders | 120 | Reconcile the list by identifier |
| Posted orders | 118 | Investigate the two remaining orders |
| Duplicate orders | 0 | Review the duplicate-prevention log |
| Unmapped items | 3 | Update the code mapping |
| Pending refunds | 2 | Follow up with the payment gateway |
If eligible orders total SAR 24,000 and documents total SAR 23,600, the difference is SAR 400. Do not post the difference as an aggregate entry before identifying the orders that caused it. One may be an advance payment or an order that has not been delivered. Multi-branch accounting software helps organize channel and branch reports where sales are shared.
A Testing Plan Before Promotional Seasons
Select ten varied products and process a paid order, a cash-on-delivery order, a discounted order, a cancellation before shipment, a partial return after delivery, and a duplicate order. Test selling the last unit in the showroom and online within a short period. If the solution does not support immediate shared reservations, establish safety stock or a review policy to reduce overselling instead of assuming that synchronization is instantaneous.
Run the tests in a suitable environment that does not affect real customer invoices. Record the expected and actual results for each case, then identify who is responsible for resolving it. Do not expand the integration before understanding how synchronization is restored when the connector stops working. Book a session to test your store scenarios.
Practical Scenarios and Advanced Reviews
How Do You Start the Integration Without Disrupting Previous Orders?
Before enabling the connector, define a clear starting point. All orders through the end of a particular day may be recorded in the old system, while synchronization begins the following day. If you import orders from previous months after enabling the integration without identifying the documents already recorded, you may duplicate revenue and tax. Create a list of open orders at the transition and determine whether they need to be transferred as orders only, invoices, or outstanding balances according to their status.
In an example of a store with 300 previous orders, 250 are completed and recorded, 30 are paid but not delivered, and 20 are cash-on-delivery orders that have not been fulfilled. Do not treat all of them as new sales. Retain the identifiers of recorded orders to prevent duplication, and transfer open cases according to a clear policy. After activation, reconcile the first batch of orders with store reports before allowing posting at scale.
Managing Shared Warehouses and Reserved Inventory
If the online store draws stock from a central warehouse while the showroom draws stock from a branch warehouse, you may need different rules for determining availability. Do not aggregate all quantities on the website if some cannot be shipped to customers. Identify the warehouses eligible for each channel, reserved stock, stock under inspection, and stock allocated to wholesale orders.
Suppose the central warehouse has 30 units, of which eight are reserved and four are under inspection, while the branch has ten units that are not allocated to the online store. If the store uses only the central warehouse, 18 units are available under these assumptions. Displaying 40 units may lead to sales that cannot be fulfilled. Test inventory transfers between warehouses and ensure that quantities do not appear in both locations during transit before receipt is approved.
Handling Cash on Delivery
For cash-on-delivery orders, shipping an order does not mean that the amount has reached the bank. The carrier may collect the amount at delivery and transfer it later, or return the shipment if the customer refuses delivery. Determine when the sale occurs according to the terms of supply and who owes the store the amount after collection. Retain the shipment number, order identifier, and settlement reference with the shipping company.
If the shipping company delivers an order worth SAR 460 and collects the amount on behalf of the store, the store may have a receivable from the carrier according to the contract. If the carrier deducts fees from the transfer, separate the fees from revenue and collections. If the customer refuses delivery, review the document status and the movement of goods when they return. Do not automatically treat all orders marked as shipped as collected sales.
Promotions, Coupons, and Gift Cards in the Store
A store may use a coupon that deducts 10% from an order, give a customer free shipping, or offer a gift card. Do not treat these tools as a single type of discount in every case. Determine the nature of the consideration, who bears the discount, and how it is allocated to line items. Review the accounting and tax treatment of cards and vouchers according to their type. The integration must transfer sufficient detail so that the accountant does not have to guess.
Example: an order worth SAR 300 before tax, a SAR 30 discount on products, and SAR 20 in shipping fees before tax. If all elements are subject to the standard rate and shipping is part of the consideration due, the total before tax becomes 290 and VAT is 43.50. If the connector transfers only the product total and omits shipping, a collection discrepancy will appear. Test cases involving a line-specific discount, an order-level discount, and additional fees.
An Integration Review Plan for Price and Product Changes
When a product price changes in the system, determine whether the online store price should update automatically or whether the marketing price remains independent. If a promotion ends at midnight, do not allow scheduled synchronization to restore the old price after the campaign ends. Retain the effective date of prices and the source of the change. When deleting a product from the store, do not delete its historical item record from the accounting system if it is linked to previous sales.
Test editing an existing product, adding a new variant, deactivating a product, and changing an SKU. Do not change the identifiers used for integration without a plan, as this may create a duplicate item. If integration fails because a product is unknown, place the order in an exceptions queue rather than posting it against a generic item that loses inventory details. Review accounting and point-of-sale solutions to determine how to manage items and channels.
How Can You Verify Integration Success After One Week of Operation?
Review a sample of completed orders from each channel and reconcile the order number, invoice, tax amount, discount, quantity, cost, and payment reference. Also select cases that were deliberately not posted, such as orders canceled before fulfillment. The difference between the number of orders and documents should be explainable, not necessarily zero in every case. Counts may differ where orders are split or legitimate corrective documents exist.
| Review case | Evidence of success |
|---|---|
| Paid order | Payment and invoice linked without duplication |
| Cash-on-delivery order | Track the carrier receivable or nondelivery status |
| Promotion | Discount, tax, and shipping reconcile |
| Last unit | Available quantity is not exceeded, or a handling procedure exists |
| Return | Note, inventory, and refund reconcile |
After the first week, identify the most frequent causes of exceptions. If most relate to product codes, fix the item mapping before increasing the number of channels. If the cause is delayed responses, review the reprocessing mechanism. In this way, integration becomes a process that can be continuously improved.
Managing Customer Data Between the Store and the System
The same customer may purchase through more than one channel using different email addresses or phone numbers. Do not merge customer records automatically merely because names are similar, and do not create a new record for every order unnecessarily. Define matching rules that preserve the data required for invoicing and customer service, and avoid transferring personal data that the system does not need. If the business uses a generic cash customer account for some retail sales, review whether this is appropriate for the invoice type and data requirements. When dealing with a business customer, verify their data before issuing the document. Customer and supplier account statements can be useful when designing receivables reports for credit orders or cases that require follow-up.
Ready to Try the System?
Start your free trial or speak with the sales team to help choose the right solution.
Frequently Asked Questions
Does Connecting Salla and Zid Mean Synchronizing Them with Each Other?
Not necessarily. The aim here is to connect each store to the accounting system, which may use shared inventory if the solution supports it.
Are All Previous Orders Transferred Automatically?
It depends on the connector. Define the integration start date and the treatment of previous orders to prevent duplicate invoices.
Can Inventory Be Synchronized in Real Time?
Some solutions support rapid updates, but delays, synchronization directions, and outages must be tested.
Who Issues the Electronic Invoice?
Identify the issuing party in the integration design according to the authority’s requirements, and avoid duplicate documents for the same supply.
How Do I Handle a Partial Return?
Link the returned line items to the original order and invoice, and review the note, tax, inventory, and refund.
Is Successful Technical Integration Enough?
No. Documents, journal entries, inventory, and collections must match actual transactions.
Conclusion
Integrating an online store with an accounting system succeeds when data sources and order statuses are defined and synchronization and returns are tested before expansion. Use the guide to cloud accounting software to understand the integrated solution, then request a practical trial using your products and channels.
Start evaluating the right system for your online store.
Manage Your Business with Greater Flexibility
Try Digital Business for free. Start issuing electronic invoices designed to meet ZATCA requirements in minutes.


