AmzForge is the software platform JIMI builds and operates. It connects to Amazon's advertising and selling partner APIs, consolidates advertising and seller operations data for the accounts that authorise it, prepares campaign recommendations for specialist review, and produces the reporting our clients receive.
One system for advertising operations and the seller data behind them.
Advertising decisions depend on seller data: stock, price, listings and settlement. AmzForge is built to hold both sides in one place, so a bid change can be seen against inventory and margin rather than in isolation.
Campaign, targeting and search term performance pulled through Amazon's advertising API for each authorised account, normalised across marketplaces and currencies into one reporting model.
AmzForge prepares structured recommendations: bid changes, negatives, budget moves, structural splits. Each one carries the reasoning behind it and waits for a specialist to approve or reject it.
Every approved change is recorded with the account, the object changed, the previous and new value, the reason, and who approved it.
Monthly reports by campaign and targeting, with placement splits, search term summaries and budget utilisation, generated from the same data the operators work from.
Role-based permissions, per-account isolation, and a full audit record of who read or changed what. Client accounts are kept separate from one another.
Listings, inventory, pricing and settlement data through Amazon's selling partner APIs, so advertising decisions can reference stock and margin directly. Being built and tested on accounts we manage before release.
Authorisation first, then data. Nothing else.
The client signs in through Login with Amazon and grants AmzForge access to their advertising account, and optionally their seller account. The client chooses the scope; consent can be withdrawn at any time from their Amazon account.
Data is retrieved through Amazon's advertising and selling partner APIs. AmzForge does not scrape the Seller Central or advertising console interface, and does not use the client's password.
Marketplace, currency, time zone and attribution differences are normalised into a consistent model. Each account's data is stored separately and keyed to that account.
AmzForge prepares recommendations; it does not apply changes on its own. A member of our advertising team reviews each one, and structural or budget changes are agreed with the client first.
What is live today, and what comes next.
Written down so there is no gap between what the site claims and what the platform does. Anything not marked live is not yet in production.
| Live | Amazon Ads data consolidation, campaign recommendations with specialist review, change log and audit trail, client reporting, role-based access control. |
|---|---|
| In development | Seller operations modules through the selling partner APIs: listings, inventory, pricing and settlement data, linked to advertising decisions. |
| Planned | Self-service onboarding for additional seller accounts outside our managed service, and a read-only reporting API for client-side integration. |
| Not offered | Autonomous bid or budget changes without human approval, automated listing creation, and DSP campaign management. |
The commercial side, and how data is handled.
Pricing - starting figures for managed advertising, with the platform included. See pricing →
Security and data - what AmzForge stores, where it is stored, and what it deliberately does not request. Security and data →
Questions - write to it@jimiyoupin.com with your marketplaces and current setup.