Platform data
Your own Amazon connection, with marketplace and period context.
Understand what sells, what needs restocking and which costs sit behind your contribution.
MELTH brings your Amazon products, sales and inventory together with your own cost files. Give your commerce, operations and finance teams the context to investigate a product and review the evidence behind a decision.
Which product needs attention? How much stock is really available? Can we trust the cost behind this calculation?
Useful answers need more than another export. They need product identity, the right period, a meaningful stock context and source values that someone has actually reviewed.
Your own Amazon connection, with marketplace and period context.
Excel and CSV files, with inspectable versions and evidence.
Ask questions, explore patterns and understand the limits of an answer.
Review proposed cost values before they become active.
Follow a finding back to the source and the decision behind it.
Start with a business question. Move through the context. Keep the evidence with the answer.
Workflow explanation. This is not a live dashboard or a claim that MELTH executes actions in Amazon.
Follow a product across its listing, inventory and sales context, without rebuilding the story from separate exports.
A canonical catalogue brings ASIN identity and associated SKU/listing context together. Product images, titles and normalised brands help your team recognise what they are looking at.
A marketplace filter describes sales context. It does not prove that every country-analysis module or every historical period is available.
Understand inventory through fulfilment pools, not a misleading sum of country totals.
Multiple marketplaces can draw on a shared European stock pool. That stock should not be counted again for every marketplace. EU and UK networks need their own context where applicable.
Local and remote pool labels need the product’s actual definition. Advice is not autonomous purchasing or a guaranteed forecast. Missing history stays incomplete.
A contribution figure is only useful when you can see what went into it.
Connect revenue with available Amazon financial events and applicable, approved cost prices. Keep currencies separate and gaps visible.
Understand proceeds after the Amazon costs available for the relevant period.
Calculate contribution where approved unit costs, currency and coverage support it.
Advertising, other business costs or missing evidence may sit outside the calculation.
Missing cost ≠ zero cost.
Different currencies ≠ one euro total.
VVP: the managed cost per sellable unit in MELTH. The product, unit, currency and effective date all matter. A single item, multipack and gift set are not interchangeable.
COGS: the cost of the units sold. Coverage: how much of the relevant data has applicable evidence. Product coverage and revenue coverage have different denominators.
Your files hold decisions, assumptions and knowledge. Bring them into a workspace where that context can be inspected.
Add Excel or CSV as a business source. Inspect worksheets, search the contents, download the original and retain its version. Set a general analysis goal or specific intended uses, and revise those uses later.
Suggested purposes can follow recognised columns. A purpose label is context, not an automatic write to another system.
Investigate supported questions such as duplicate SKUs or which currencies are present. Review the source version, worksheet and analysis coverage with the answer.
Open questions may use column structure and a labelled sample. An AI explanation does not imply that every row was analysed.
The concrete cost-price review chain within MELTH:
The file, version and evidence rows.
Product match, unit, value and validity. A normalised source if needed.
Inspect the evidence. Approve eligible values or leave questions open.
The approved basis flows into product detail and applicable calculations.
Approve one suitable proposal, explicitly selected suitable rows, or all ready and eligible proposals. A filter is not approval of hidden rows. Unresolved and batch exceptions do not silently become accepted costs.
Reject a pending proposal. Correct or withdraw an individual accepted value. Preserve the previous value, reason and source history. A replacement is different from a withdrawal; bulk withdrawal is not claimed.
Follow an active value through the decision, evidence rows and source version. Where an intermediate normalised source exists, retain the path back to the original file. Open cost questions stay visible.
Know which data you are using, how recently it was updated and what has actually been approved.
Customer-owned Amazon authorisation and customer-scoped data and sources. The described Amazon integration reads data; it does not execute changes.
Automatic synchronisation brings platform data into MELTH. Check the relevant update time and available history before drawing conclusions.
Source versions, evidence and review history help reconstruct the decision. No blanket claim that every external system is audited.
Move from contribution to product detail, then to the applicable cost source and original version. Review which costs and currencies the figure covers.
Follow the calculation ↗Start with a period and product filter. Inspect performance, the fulfilment pool, weekly sales and coverage before your stock discussion.
Understand the context ↗Inspect the file, product match and unit. Review suitable proposals. If an approved value is wrong, correct or withdraw it with history retained.
Explore the review chain ↗Make your current files understandable first. Build a more deliberate process from there.
Excel/CSV → inspection and analysis → supported mapping and proposals → human review → managed cost prices inside MELTH → traceable product and contribution calculations.
Over time, this foundation can support a transition towards systems such as Odoo or Zoho. Migration and external execution require their own validated connectors, permissions, checks and recovery paths.
Next-stage work: Buy Box, expanded marketplace/country analysis, Deals, Advertising, a full alerts module and additional source connectors. These are not presented here as completed features. Scope is confirmed for each selected workspace.
No. The Amazon connection described here is read-only. It does not change prices, listings, inventory, shipments or advertising. Data synchronisation is separate from permission to execute business actions.
The connection is periodically updated. Freshness information helps you check the latest update for the relevant data. Coverage and available history depend on the source; a connection is not a real-time guarantee.
Yes. Excel (.xlsx) and CSV files can be added as business sources, inspected and analysed. You can select or change their intended uses. A purpose such as CRM or marketing is source metadata, not proof of an implemented import or connector for that process.
VVP is the managed cost per sellable unit in MELTH, with a relevant currency and effective date. COGS means the cost of the units sold. Coverage describes how much of the relevant dataset has usable cost evidence. Product coverage and revenue coverage measure different things.
No. Contribution uses the available Amazon costs and applicable approved cost prices. Missing costs, incompatible currencies and incomplete coverage limit what can be calculated. Advertising is a future integration phase; full business profit is not claimed.
Not for every question. Supported calculations can answer specific questions such as duplicate SKUs or currencies present. Open-ended analysis may use column structure and a labelled sample. Check the source version, coverage and limitations shown with the answer.
An individual approved value can be corrected or withdrawn with its history retained. Rejecting a pending proposal and withdrawing an accepted value are different actions. Bulk withdrawal is not part of the scope described here.
Amazon is the concrete application described on this page. Buy Box, expanded country analysis, Deals, Advertising and a full alerts module are next-stage work in the supplied product checkpoint. Other channels and external execution require their own verified integrations.
MELTH works with selected B2B clients. Submit your business context, challenge and motivation through the application form. Every application is reviewed personally; access is not automatic.
Tell us about your business, the problem you want to solve and why now. We personally review each application and choose the clients we work with.
Discuss your e-commerce case ↗Application → personal review → invitation if there is a fit.