Connect your suppliers to your stores. AI helps prepare data, translate attributes and search for products. Your rules govern pricing, stock and publication.
Your suppliers and stores, finally on the same wavelength.
| Product | Supplier price | Your price | Stock | Publication |
|---|---|---|---|---|
16-inch laptopDEMO-PC-016 | 649,00 € | 799,00 € | 42 | Up to date |
Logitech MX Master 3S910-006559 | 61,50 € | 84,90 € | 128 | Up to date |
Samsung ViewFinity S6LS27D600UAUXEN | 189,00 € | 239,00 € | 16 | To review |
You keep your tools. HarvestFlow connects their data.
Between the supplier file and the price displayed in your store, every manual step becomes something to monitor.
An overlooked selling price can reduce your margin. HarvestFlow recalculates prices according to your rules and flags discrepancies below your floor.
Availability does not stay in the latest file received. Send stock levels to compatible stores on the update schedule agreed together.
Map your file columns to your store fields. Reuse this configuration to import changes and publish selected products.
AI helps your team understand files, adapt attributes and find the right products. Your business rules guide the actions.
Analyse the structure of a supplier file and get help mapping its columns. Check the mappings before reusing your configuration.
Mapping assistance availableTranslate attribute names and their short text values. Reuse your editorial dictionary and available multilingual content first.
Assisted translation availableCombine text search, semantic search and natural language to explore your catalogue. Then refine the results using your filters and saved views.
Intelligent search availableAPIs, compatible webhooks, structured operations and activity history: HarvestFlow provides building blocks for workflows driven by AI agents or your automation tools.
Together, we define accessible actions, permissions and human approvals. Agent integration is assessed on a project basis; no universal MCP connector is offered today.
Assess my agent workflowThe same product references are used to enrich listings, calculate prices and publish updates. You configure the workflow; HarvestFlow runs the defined steps.
Every supplier has its own format. Map its columns to your product data, then reuse the configuration. Changes enter your central catalogue before being sent to your stores.
Enriched listings, search, pricing, orders and monitoring: explore the features supporting every stage of your business.
Combine data from your suppliers, product catalogues and compatible manufacturer sources to build a more complete product listing.
Adapt attributes to your store's language and reuse multilingual catalogue content.
Decide which products to publish and which information to send to each channel.
Find products by keyword, product reference or identifier without browsing the entire catalogue.
Describe your needs in natural language or explore products by meaning.
Prepare your working selections and return to them without reconfiguring the list on every visit.
Track Odoo and Amazon orders, their processing and shipping information.
Connect your store's order to direct shipping by the supplier.
Receive supplier events to trigger an update without waiting for the next file.
Monitor feeds, tasks and platform health from the dashboard.
Identify products withdrawn by the supplier and avoid keeping obsolete products on sale.
Review data changes and the actions that explain a product's current state.
View purchase costs, fees, your price floor, the published price and reference offers. Then choose the pricing factor or strategy to apply to a product or selection.
A source being included in the project does not mean its prices are already being collected.
Competing offers, Buy Box and lowest prices available for matched products. Also compare your displayed price with the price calculated by HarvestFlow.
Read access through your seller account and SP-API permissions; availability and frequency depend on Amazon.View serviceA potential benchmark for comparing a product with a market price from Google Shopping.
Configuration and connection testing are implemented. Benchmark collection and its use in repricing are not yet integrated.View serviceA price comparison option to explore, particularly for IT in Germany and Austria.
No active data collection in HarvestFlow. Data access must be assessed before any integration.View serviceAccess and formats vary. Discover supported sources and options to explore before defining your project.
Bring together the steps your team needs and identify orders requiring attention, through to the carrier and tracking number.
Channel orders are retrieved periodically.
Eligible order lines follow the configured workflow.
The order is forwarded for direct shipping.
Carrier, tracking and confirmation are sent back to the channel.
Dropshipping: workflow validated in testing on one supplier connection, to be confirmed in a live pilot. Channels, access rights and the supplier must be compatible with the proposed workflow.
A scheduled file for regular updates, an API query to check a value, a webhook to process an event as it arrives: these methods complement each other depending on the supplier.
Assess my event-driven updatesThe webhook requires registration of the supplier callback, a public receiving endpoint and a configured signature. Event processing depends on events being sent and on the connected services; there is no promise of real-time updates across all sources.
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.
The import, enrichment and publication workflow is used in a real store. The pilot programme now checks how this workflow fits your files, pricing rules and channels.
Discover the HarvestFlow approachimported products
products published in a real store
Before discussing deployment, we check the available data, the rules to apply and the results you expect in your store.
We examine a supplier file sample and the products you want in your stores.
We specify the products to publish, price calculations and update frequency.
You see the workflow with your own data and identify where adaptations are needed.
You receive a pilot scope and quotation to decide on the next steps.
When your products, prices and stock come from several files or services, a central catalogue can simplify preparation. Sources and industry data are validated sector by sector.
Distributor prices, catalogue content and manufacturer specifications: centralise data to prepare publication in your store. One workflow is already in use with Odoo.
Product references, images, prices & availabilityLet's discuss my sectorStart with a supplier file to structure product references and prices. Specialist catalogues and vehicle compatibility remain to be assessed.
Supplier files · industry data to be assessedLet's discuss my sectorVaried product ranges and suppliers, with attributes to organise and price changes to pass on.
File formats and content need to be validatedLet's discuss my sectorParts, consumables and equipment: explore a central catalogue and product selection rules specific to your channels.
Imports, categories and prices by storeLet's discuss my sectorAn option to explore for retailers whose suppliers provide reusable product references, prices and content.
Content rights and variants need to be checkedLet's discuss my sectorBring together data for your product ranges and prepare selections by store or season, based on your sources.
Product scope and connectors to be assessedLet's discuss my sectorA potential sector does not mean a specialist catalogue or supplier connector already exists. Attributes, variants, licences and business rules are assessed before confirming your scope.
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.