Maiju Data is a software service for Amazon sellers. It collects a seller's own sales, advertising and inventory data every day, then shows which listing needs attention, which search term is spending without converting, and which SKU is close to running out.
Request a demo See pricingFour working areas, one database. A seller connects their own account, chooses what to sync, and keeps full control of the data.
Orders, returns and settlement records are collected daily and reconciled into a single profit view per SKU and per listing, so a weekly or monthly review takes minutes instead of an afternoon of spreadsheet work.
Campaign, keyword, search term and placement reports are stored day by day, so spend trends stay visible instead of resetting with every report window. The platform flags search terms that spend without converting and prepares bid and negative-keyword candidates for a person to approve.
Fulfilment centre stock, inbound shipments and local stock are tracked together against real sales velocity, so a restock decision is based on days of cover rather than a snapshot number.
The day-to-day work around the numbers: tracking inbound shipments to the fulfilment centre, grouping return reasons so quality problems surface early, and keeping the follow-up items from each review in one shared list.
More questions? Write to support@maiju.work.
Through the official APIs, using the standard OAuth authorisation flow. You sign in on the platform's own authorisation page and approve the connection there. Maiju Data never asks for, never sees and never stores your account password.
Authorisation is per account and can be revoked by you at any time, from your own account settings, without contacting us.
What we read: business operating data only — order and return statistics, settlement and fee records, inventory and inbound shipments, listing and catalogue attributes, and advertising reports down to the search term. All of it is non-PII.
What we never read or store: buyer names, shipping addresses, phone numbers, email addresses, or any other consumer personal information. We do not request the restricted data roles that would grant access to it. Where a data feed could contain such fields, they are discarded before anything is written to our database, logs or backups.
Data in transit is encrypted with TLS 1.2 or higher. Data at rest, including backups, is encrypted with AES-256. Authorisation tokens are held in encrypted server-side configuration, are never exposed to a browser and are never written to application logs.
Each seller's data sits in a separate logical dataset, reachable only by the users that seller has authorised. Inside the product, access is controlled by role and by page, and member actions are recorded in an audit log. We do not sell your data, do not share it with other customers, and do not use it to train models for anyone else.
Revoking authorisation takes effect immediately and we stop retrieving new data at that moment. Stored data — including backups — is permanently deleted within 7 days of revocation, account closure, or a deletion request sent to support@maiju.work. We confirm in writing once deletion is complete.
You can export your data at any time while the account is active. Full detail is in the Privacy Policy.
No. Maiju Data is an analysis tool, not an agent. Suggestions such as bid changes or negative keywords are presented for review and applied only when someone in your team chooses to apply them. It does not place orders and does not make bulk automated changes on its own.
A seller authorises their own account through the standard authorisation flow, chooses the data to sync, and can revoke access at any time from their own account settings. There is no manual file upload and no shared login.
Email support@maiju.work