Before you import
An Amazon ASIN identifies a catalog item, but the same identifier can exist in more than one marketplace. Review Magic therefore treats ASIN plus marketplace as the listing identity and also pins that listing to one legal client and one brand.
For multi-brand accounts, prepare the brand mapping before approval. An import never silently moves an existing listing from one brand to another.
- Use the 10-character ASIN, not a product title or Seller SKU by itself.
- Choose the marketplace where the reviews actually appear.
- Map every row to a child brand owned by the active legal client.
- Remove duplicate rows before approval; do not use duplicates to request faster processing.
Choose an import method
| Method | Best for | What to expect |
|---|---|---|
| Add one listing | A quick correction or a small account | Immediate validation against the active client and brand. |
| Paste or CSV upload | Planned multi-brand onboarding | A staged manifest you can validate, finalize, approve, and commit. |
| Seller Central report | A larger existing Amazon catalog | Use the exported rows, then confirm marketplace and brand mapping. |
| Amazon SP-API connection | Future ongoing catalog synchronization | Available only after Review Magic’s production connector is configured and authorized. |
How large imports stay safe
A staged import can contain up to 10,000 listing rows. Upload requests are bounded, and the commit applies rows in resumable batches rather than holding one long request open.
The approved manifest freezes the legal client, brand assignments, marketplaces, and source details. The portal currently requests each 200-row commit step. If the tab closes or the network drops, progress pauses at the recorded checkpoint and can resume from the existing import; it does not restart from row one.
- Up to 2,000 rows per staging request.
- Up to 10,000 rows in one complete import.
- Commit progress is checkpointed in 200-row units.
- A lease prevents two workers from committing the same import at once.
- Plan-capacity overflow remains visible as paused instead of being discarded.
Import 40–100 brands in one agency manifest
Agency owners and managers can use one CSV or tab-separated paste with client_key, brand_key, asin, and marketplace columns. seller_sku and source_status are optional. A missing source status means active; an unrecognized or explicitly unknown status must be corrected before approval.
Review Magic resolves client_key only against the current agency’s active, client-authorized relationships. It resolves brand_key only inside that legal client, using the brand’s stable external reference or slug. A mutable client or brand name is never treated as access authority.
Finalization validates the complete manifest and reports every row error without creating a client catalog import or changing a listing. Approval pins one exact manifest hash. Execution then creates immutable child imports partitioned by legal client and brand; it never sends or processes a mixed-tenant provider batch.
- Duplicate rows, conflicting brand assignments, unknown keys, revoked clients, unsupported marketplaces, and existing cross-brand ownership are reported before approval.
- An interrupted upload can resume with the same source file after its staged prefix is verified.
- An interrupted execution resumes from each child import and committed-row checkpoint.
- Client authorization is checked again immediately before every child mutation. Revoked clients remain blocked while unrelated authorized children can finish.
- Agency analysts can inspect and export manifests but cannot create, approve, or execute them.
Accepted listings can finish in a different order
After the catalog commit, Review Magic admits independent listing jobs with bounded concurrency. Work is rotated across legal clients and brands so one large portfolio does not occupy every processing slot. A smaller or faster listing may finish before an earlier row; the portal sorts the resulting records for you after each state change.
You can open a queued listing while processing continues. Do not re-import it to move it ahead. Review Magic does not show a fixed countdown because provider response time, daily cost limits, retry behavior, and review volume can change the real completion time.
| Stage | What is ready | What can happen next |
|---|---|---|
| Catalog accepted | Client, brand, marketplace, and listing identity are stored. | The listing waits for fair queue admission. |
| Queued | The listing remains visible and inspectable. | Capacity, platform, account, and cost gates are checked before provider work. |
| Collecting listing data | Amazon metadata and an initial 1–3★ source scan are running. | Independent listings may complete out of order. |
| Scan collected; processing | The provider work is stored, but review normalization and analysis have not settled yet. | The listing remains visible while downstream processing continues. |
| Actionable scan ready | The initial 1–3★ source data has been normalized and analysis has settled, with any terminal exceptions recorded. | Scheduled monitoring can proceed while lower-priority history enrichment continues. |
| Monitoring | The initial actionable work is ready and the listing is eligible under its current account and listing state. | Scheduled checks continue according to the listing policy. |
Paused, suppressed, and discontinued listings
Review Magic keeps listing history when a product is temporarily suppressed, discontinued, source-inactive, or above plan capacity. Those listings do not need to be deleted and recreated.
A later source sync or manual action can reactivate an eligible listing. A user pause remains a separate instruction and is not silently cleared by a source update.
| State | What it means | What to do |
|---|---|---|
| Active | Eligible for scheduled monitoring. | No action unless the marketplace or brand is wrong. |
| Paused by user | A person intentionally stopped monitoring. | Reactivate when you want monitoring to resume. |
| Paused by source | The connected catalog reports it as inactive, suppressed, or discontinued. | Correct it at the source, then sync or reactivate when active again. |
| Paused by plan limit | The listing is retained but exceeds current active capacity. | Pause another listing or change capacity before reactivation. |
About Amazon account connections
An SP-API connection belongs to the legal client’s seller account, not to a single brand. Imported listings still require an explicit mapping to one child brand.
When configured, catalog preview advances through a bounded number of sequential marketplace pages per request. Each page chunk is stored in a client-and-connection-scoped snapshot for 24 hours. Rate limits and transient provider failures use bounded retry and Retry-After handling; closing the tab preserves the last durable cursor.
Sync consumes that stored snapshot instead of downloading the catalog again. A complete, untruncated snapshot is required before bulk-all reconciliation. Snapshot IDs cannot be reused across legal clients or Seller connections.
Review Magic will never ask you to share a Seller Central password. Amazon authorization uses Amazon’s consent flow and revocable credentials. Until the production connector is enabled, use ASIN, CSV, or Seller Central report import.
Continue the task