What is included

Different data is exchanged at different frequencies. Pushing the whole catalogue every fifteen minutes is pointless and heavy.

Discuss the scope

Catalogue export

Sections, products, specifications and images. Usually once or twice a day.

Prices

The main price, the struck-through price and contract prices for specific clients. Every one to four hours.

Stock

Most frequent of all: at least hourly. Less often and a customer pays for something you do not have.

Orders

From the site into accounting with the customer details, delivery and payment method.

Statuses

Back to the site so the customer can see what is happening and does not phone.

Monitoring

Exchange error alerts to a real person rather than into a log file.

How the work runs

A standard exchange takes one to two weeks. A customised configuration with non-standard entities takes a month or more.

01

Assessment

We review the configuration, the warehouses, the price types and the state of the product list.

02

Test environment

We set the exchange up on a copy of the database. The first exchange on a live database rarely goes smoothly.

03

Debugging

We compare what was exported against the source and catch discrepancies in units, prices and specifications.

04

Go-live

We move it to the live database, set the schedule and switch on the alerts.

The readiness of the product list determines the project timeline more than the complexity of the exchange. Duplicate items, specifications buried inside names and a catalogue structured for accounting are a week of work for a product manager, and it has to happen before the setup, not after.

Frequently asked questions

Almost always, the question is the amount of work. A standard configuration exchanges data almost out of the box; a heavily rewritten one needs a bespoke handler. We give a definite answer after looking at the configuration rather than from a description.

Not with a sensible schedule. A full catalogue export is set for the night and incremental exchanges run quickly. Problems arise when an export coincides with period closing or scheduled jobs, and those are separated in time.

An alert fires and the exchange repeats on schedule. The important part is that a failure does not go unnoticed: a site with week-old prices is worse than a site with no prices.

We will set up the exchange with 1C

Tell us about your configuration, the number of products and the warehouses. We will look at the database and estimate the work.