Compare the proposed scopes, then let's validate the sources, volumes and channels you actually need.
One store to supply or several suppliers to coordinate: the right starting point depends on your catalogue and the connections required.
You have one supplier and up to two channels to keep up to date.
FromYou manage several suppliers and want to control your margins.
FromYour catalogue and feeds require enhanced support.
FromIndicative prices excluding VAT, subject to change during the pilot programme. Scope, availability and terms confirmed by quotation. Store and third-party licences not included. ¹ Target volume to be validated for your catalogue.
Free proposed at 0 € · 250–500 products, 1 supplier, 1 channel.
Enterprise and on-premises hosting: assessed by quotation.
Your project has its own requirements.
We are here to discuss it.
No. HarvestFlow complements your existing store. You keep your Odoo, Magento or Amazon seller account and centralise supplier data and publication rules in HarvestFlow.
No. A CSV, XLSX or JSON file may be enough. Depending on your supplier, we assess manual upload, HTTP download or retrieval from an SFTP/FTP server. The format and frequency are validated during the pilot.
We start with a sample supplier file, your product volume and your sales channels. The demonstration checks the mappings between data, pricing rules and supported operations before defining a pilot.
You define the calculation rules used for publication. A price floor alert never changes a price on its own. Competitive positioning proposals are applied by the operator.
Files can be imported on a schedule and APIs queried within their limits. Webhooks allow prices and stock to be processed when an event arrives, for suppliers with a compatible connector. They must be activated and registered with the supplier. Frequency depends on the connected services.
Today, automatic translation adapts attribute names and their short text values to the store's language. Multilingual descriptions and titles are taken from catalogues where available. Full automatic translation of every title and description is not currently included.
Yes. You can combine data from your suppliers, compatible product catalogues and supported manufacturer sources. You define field mappings and priorities. Fallback fields allow another source to be used when a value is empty. Available content depends on the product reference and your account rights.
Price calculations follow the rules you choose. For competitive positioning, the operator compares benchmarks and applies a strategy or pricing factor. Amazon is used for price references; Google Merchant Center is in preparation and Geizhals remains to be assessed.
The workflow connects orders from supported channels to a compatible supplier, then retrieves the carrier and tracking information and confirms dispatch. Validated in testing on one supplier workflow, it must be confirmed in a live pilot using your access credentials. Compatibility is checked for each store-supplier pair.
HarvestFlow detects products removed from files. In compatible workflows, a check against the supplier API confirms withdrawal before automatic archiving. A product simply missing from a file is not treated as permanently discontinued without verification. Processing varies by channel.
No. You select products to publish using rules specific to each store. The pilot can focus on a selection of products to check prices, stock and listings before expanding the scope.
The Amazon connector publishes offers on catalogue listings that already exist. Matching uses EAN codes. It does not create new Amazon catalogue listings.
No. Your store, supplier accounts and data licences remain in your name and at your expense. This includes sales platforms and any specialist catalogues or licensed data services.
HarvestFlow supports local Ollama or a compatible cloud AI provider. Deployment within your infrastructure is assessed by quotation, starting from the Growth scope, under a commercial licence.
Data sources, available connectors, products to publish, pricing rules and update frequency. Displayed prices are indicative: scope, support and terms are confirmed by quotation before you commit.
Show us a sample catalogue and your store.
Let's check which updates you could automate.