The catalogue
Categories, products, attributes, images. Once or twice a day is enough.
Different data needs different frequencies. Pushing the full product list every fifteen minutes is unnecessary and harmful to the database.
Categories, products, attributes, images. Once or twice a day is enough.
Base, struck-through and contract prices for wholesale customers. Updated every one to four hours.
The most frequent flow, hourly at minimum. Any rarer and a customer will pay for something you do not have.
They go into the database together with the customer details, the chosen delivery and payment method.
They come back to the storefront so the customer sees progress and does not ring to ask.
When the exchange fails, the responsible employee finds out rather than a log file on the server.
A standard integration is configured in one or two weeks. A customised configuration with non-standard entities takes a month or more.
We look at the configuration, the warehouse structure, the price types and the state of the product catalogue.
The integration is configured on a copy. A first run straight on the live database almost never goes smoothly.
We compare what was exported against the source and look for discrepancies in units, prices and attributes.
We switch it on, set the schedule and connect alerts to the responsible person.
Product attributes written into the name break the filters on the storefront. Colour, size and volume have to sit in separate fields, otherwise faceted search cannot be built and the customer will not find what they want. Sorting out the catalogue is the merchandiser's job and is done before the integration is configured.
Almost always; the difference is only in effort. An unmodified configuration connects with the standard tools, while a heavily rewritten one needs its own handler. We answer after looking at the configuration rather than from a verbal description.
With a sensible schedule, no. The full catalogue export runs overnight and the short exchanges take seconds. Problems begin when the export collides with month-end closing or the nightly maintenance jobs, and those are separated in time.
An alert arrives and the exchange repeats at the next scheduled time. What matters is not missing the stoppage itself: a storefront with week-old prices is worse than one with no prices at all.
Tell us the configuration, the number of products and the warehouse structure. We will look at the database and assess the effort.
Request received
It is already with a manager. You will get an answer within the working day, and urgent requests go to the duty engineer immediately.
There is no such city in the list. Check the spelling.