Skip to content
095 430-06-28Consultation095 430-06-28

Integration with BAS for a website and online store

BAS integration sends products, prices and stock from your accounting system to the site and creates online store orders in BAS without manual entry. The feature set depends on the BAS configuration and the site platform, so we clarify it during the audit before work begins.

  • product catalog, prices by type and stock by warehouse from BAS on the site;
  • orders from the site in BAS: customer, items, delivery, payment method;
  • payment and shipment statuses returned to the site;
  • product matching by SKU and duplicate control;
  • exchange on Horoshop via the platform API, on WordPress and custom sites via a module or service;
  • testing on a copy of the database and on test orders.

How an online store works with BAS and why the exchange saves time

Companies that keep their accounting in BAS search for website integration with BAS and online store exchange with BAS when they can no longer keep up with updating stock and taking orders manually. The manager works in one system: an order from the site appears in BAS, and the accountant and the warehouse see it in the familiar format. The customer sees prices and stock on the site based on accounting data.

BAS configurations differ in their set of documents and reference data, and this determines which data is available for exchange. We clarify this together with your system administrator.

What BAS integration includes

  • export of the product catalog, prices by type and stock by warehouse;
  • creation of an order in BAS after checkout on the site;
  • transfer of the customer, contacts, delivery and payment method;
  • payment and shipment statuses returned to the site;
  • product matching rules: SKU, code, barcode;
  • exchange log, discrepancy report and failure notifications.

On Horoshop, catalog sections are added manually in the admin panel, so the exchange works with the existing structure. The connection uses the platform API; on WordPress and custom sites we connect a module or write a separate exchange service.

How we connect BAS to the site

  1. we find out the BAS configuration, version and how the database is accessed;
  2. we agree on the rules: what comes from BAS and what is edited on the site;
  3. we set up the exchange on a test copy of the database;
  4. we run test orders with different payment and delivery methods;
  5. we turn on the scheduled exchange and reconcile the first documents.

The timeline depends on the BAS configuration, catalog size and the number of scenarios; we give an estimate after the consultation.

How much BAS integration costs

We determine the integration cost after a free consultation and audit, because it depends on the BAS configuration, the site platform and the number of exchange scenarios. The work is done under a fixed-price contract; the domain and admin panel belong to you. For a new store, the catalog structure should be planned with the accounting exchange in mind, so see online store development and launch. If your store runs on another platform, it is convenient to set up the exchange together with moving to Horoshop. You can send questions about the integration via the Contacts page.

Questions and answers

How is BAS integration different from a manual price list import?

Manual import requires exporting a file and uploading it to the site every time. Integration runs on a schedule, matches products by rules and passes orders to the accounting system.

Can paid and unpaid orders be sent to BAS?

Yes, we send all orders with the corresponding payment status; we agree on the rules for prepayment and cash on delivery with your accountant.

Who makes changes to the BAS configuration?

Changes to the system itself are made by your administrator or service provider. We prepare the exchange format, the site side and clear data requirements.

What happens to the exchange if you update your BAS version?

Let us know before the update: we check the exchange on a test copy and adjust the settings if needed. This reduces the risk of failures in the live database.