A customer buys an item that is no longer in stock
We push stock levels from your system to the store on a schedule or close to real time. We agree with you which warehouse and which stock type (available or reserved) the site should show.
Your store and your back office run on the same data: stock, prices and orders sync automatically
We connect your online store to your ERP or accounting system. Stock and prices on the site match your records, and orders arrive in the back office without re-typing. It is the link between the site and the routine behind it, the part of «website, customers and automation» that removes manual work after the sale.
Quote and schedule after your brief
Who it's for
- Stores where staff copy orders into ERP or accounting by hand
- Owners who have sold items that were already out of stock
- Businesses with several warehouses or sales channels
- Companies that manage prices in the back office but update the site from spreadsheets
Problems we solve
Prices on the site and in the ERP don't match
We make your back office the single source of prices. Multiple price lists are supported, such as retail, wholesale and promo. We define how discounts and rounding behave.
Someone retypes every order into the ERP
Orders from the store are created in your system automatically with customer, items, payment and shipping. Order statuses flow back so customers see real progress.
The catalog turns into a mess after the first sync
Before launch we match SKUs, units of measure and product groups. Duplicates and items without a SKU appear in a report so you can fix them at the source.
What's included
- Audit of your ERP or accounting setup and your store platform
- Sync map: what moves, in which direction and how often
- Stock sync across warehouses
- Price sync, including multiple price lists
- Order transfer from store to back office (customer, items, payment, shipping)
- Order status updates back to the store
- Product matching by SKU or code, with a mismatch report
- Sync error log and alerts when an exchange stops
- Testing on a copy of your data before going live
- Documentation and a short walkthrough for your team
Choose the scope
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
01
Basic sync
A small store with one warehouse and a standard ERP or accounting setup
- Stock and prices from back office to store
- One warehouse, one price list
- SKU matching
- Test run and documentation
02
Full cycle
A store that needs orders to reach the back office automatically
- Everything in Basic sync
- Orders from store to back office
- Order statuses back to the store
- Multiple price lists
- Error log and alerts
03
Complex integration
Several warehouses, a custom setup or ERP, or non-standard pricing logic
- Everything in Full cycle
- Multiple warehouses and sales channels
- Custom fields and configuration changes
- ERP integration via API (a way for programs to exchange data)
- Trial period with fixes
How we work
Brief and requirements
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
Sync map and KPI pilot
We agree what moves where. We set a measurable pilot KPI, for example orders that reach the back office without manual corrections.
Build on a data copy
We build the sync on a test copy so live data stays untouched. We test typical and edge cases: returns, partial payment, out-of-stock items.
Launch and first load
We move the setup to production and run the first full catalog and stock load. We watch the sync log closely for the first days.
Training and handover
We show your team how the new statuses work. All accounts, files and access belong to you under the agreed terms.
Scope and limits
- We don't promise a clean sync with a messy product catalog: duplicates and missing SKUs must be fixed at the source
- We don't promise instant stock updates on every setup: frequency depends on your system version and server
- We don't change your accounting logic or give tax or bookkeeping advice
FAQ
Which systems do you work with?
Common ERP and accounting systems that offer an API or standard exchange formats. We confirm after the audit. If there is no ready method, we list the extra development as a separate line in the estimate.
What do you need from me to start?
Access to a test copy of your data, a list of warehouses and price lists, and a contact who knows how your records are kept. We also need admin access to the store. All access stays yours.
Will my store go offline during the integration?
No. We work on a data copy and a test environment. We switch to production at an agreed time, usually when traffic is low.
How fast do stock levels update?
It depends on your setup and catalog size. The sync can run on a schedule, for example every few minutes, and after each change where the system allows it. We fix the exact frequency in the sync map.
What happens if the sync breaks?
The log records the error and you get an alert. Common causes are a changed SKU, a locked database or a system update. After launch we can support the sync under a separate agreement.
How do payments work?
Payment terms are agreed with the quote before work starts. For a staged project, we describe the result and acceptance criteria for each stage. Support and third-party services are listed separately.
Start with your task
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.