REAL PROJECTE-COMMERCE
Store Integration with 1C and Nova Poshta.
Client under NDA. Stock and order status sync instead of manual exports.
A real project with the client under NDA: no name, screenshots or client data. The cover diagram is generalised.
- TYPE
- REAL PROJECT
- TIMELINE
- 3 weeks
- TEAM
- Tech lead, backend developer, QA
- SERVICE
- Backend / Laravel
01
Task
The client manually exported stock levels and order statuses between the store and 1C. It took hours every week and caused discrepancies: items were sold after they had run out in the warehouse, and managers copied delivery statuses from the Nova Poshta dashboard by hand.
02
Constraints
- [WARN]1C stays the main accounting system: its logic is not changed
- [WARN]The store keeps running with no downtime during rollout
- [WARN]The 1C API responds slowly and is sometimes unavailable
- [WARN]Managers must see what was synced and when
03
Solution
We built a queue-based sync of stock levels and order statuses between the Laravel store and 1C via API, with no manual export. Every operation is a separate queued job with retries, and delivery statuses are pulled from the Nova Poshta API automatically.
Scheduled stock syncA background job fetches stock changes from 1C and updates only the changed products.
Two-way statusesA new order goes to 1C immediately; a status change in 1C comes back to the store.
Nova PoshtaThe waybill is created from the order, and the delivery status updates without a manager.
Log and retriesEvery sync is logged; an API failure means a retry, not a lost order.
04
Stack
Laravelstore, integration APIQueuesbackground jobs, retriesRedisqueues1Caccounting and stockNova Poshta APIwaybills and statusesPostgreSQLsync log
05
Results in numbers
TIME SAVED−6 h / week[PASS] manual export removed
STOCK DISCREPANCIES0[PASS] after launch
Client data: managers' time estimate before and after launch, stock reconciliation over the first month.
06
What we would do differently
01We would start with the sync log: it helped most when sorting out disputed cases with managers.
02We would agree on a test copy of 1C earlier: some scenarios were checked on the live database at night.
03We would add Telegram alerts about sync failures in the first release, not the second.
NEXT CASEDental Clinic Website Redesign
DESIGN CONCEPT