SHOPFLIX Eshop integration: offers, quantities and preparation time

A SHOPFLIX integration begins with a sound catalogue and reliable offer updates. Price is only part of an offer: quantity and preparation time determine whether a sale can actually be fulfilled. Order automation must be scoped against the access and current technical instructions provided during merchant onboarding, rather than assuming undocumented capabilities from the public product-feed guide.

The official guide describes an initial product list in XML or XLSX and recurring XML updates. We map SKUs, EANs, manufacturer information, images and descriptions. Missing values should not be invented simply to pass validation. Products without suitable identifiers become preparation tasks, allowing the commercial team to resolve them before publication instead of creating unreliable catalogue matches.

Offer updates carry price, available quantity and shipping lead time. Published quantity must account for reservations made through other channels. Warehouse staff establish a realistic preparation commitment. An item available only at a supplier is not automatically equivalent to stock ready in the merchant warehouse. The connector needs to respect the sourcing and fulfillment process agreed with the marketplace.

Cut-off times and operating days affect order preparation. The design accounts for picking completion and parcel collection times. A connector that updates prices but ignores warehouse operations can create fulfillment difficulties. We assess the public offer-feed workflow separately from order actions available to the merchant account, and confirm responsibilities for accepting, preparing and handling exceptional orders during onboarding.

An Eshop sells its own stocked items alongside products sourced after purchase. The connector distinguishes these cases and assigns agreed preparation times to each group. A sale reduces the quantity offered, without publishing unconfirmed supplier availability. Pilot testing includes orders before and after cut-off and products that become unavailable. Rollout proceeds only after staff confirm that displayed preparation times match actual work. This is a proposed implementation scenario, not a statement that an existing merchant achieved a particular result.

Tests cover positive and zero quantities, changed prices, scheduled promotions and images without watermarks. Failed updates must be visible to support staff. Update frequency is agreed with the platform and the expected change rate. The public guide recommends regular refreshes, ideally every thirty or sixty minutes; that does not establish a promise that each submitted change is processed instantly. Monitoring should distinguish file creation from successful platform consumption.