Organization accounts
Registration, sign-in, token rotation, tenant isolation and role-aware access provide the core account boundary.
Product scope
Know exactly what the beta can do.
OmniSeller separates implemented product behavior, external integration verification and future roadmap work. A screen in the navigation is not treated as a finished capability.
Current verification boundary: the core product paths have automated tests and local verification. A production SP-API application, public HTTPS OAuth handoff and complete live Amazon account synchronization are still required before general availability.
Implemented foundation
Workflows already represented in the product.
These capabilities exist in the current codebase. Their Amazon-dependent portions remain gated until the production connection is approved and verified.
Seller authorization flow
OmniSeller prepares authorization state, exchanges authorization codes and stores the long-lived refresh credential encrypted.
Marketplace discovery
After successful authorization, the Sellers API path identifies the active marketplaces associated with the seller.
Listing synchronization
The Reports pipeline requests the seller's listing report and records SKU, ASIN, title, price, quantity and status.
Evidence-based listing audit
Known fields support explicit checks. Content or keyword quality is not scored when the necessary data is unavailable.
Profitability scenarios
Model sale price, product costs, fulfillment, advertising, returns and storage against a versioned fee schedule.
Status language
No ambiguous “complete” badge.
A capability moves from implemented to verified only after it has been exercised against the real dependency under production-like conditions.
Account and tenant foundation
ImplementedAvailable in the application code and covered by automated tests.
Listing audit and profitability
ImplementedAvailable with the data and verified rate schedules that the environment contains.
SP-API authorization and reports
Integration verificationCode paths exist. Amazon registration, credentials, public redirect infrastructure and a real end-to-end run remain necessary.
Automated billing and plan limits
Beta operationsPricing is published, while subscription activation and plan entitlements are handled manually during the private beta.
Product discovery
PlannedRequires market-wide product data that the seller-scoped SP-API does not provide.
Keyword gap
PlannedRequires an approved Amazon Ads or third-party keyword data source.
Scheduled alerts
PlannedRequires a durable job queue and scheduling layer before alerts can be reliable.
Automated repricing
Not offeredOmniSeller does not currently change prices or listings in the seller account.
Data currently in scope
Seller-owned catalog information.
Current beta scope focuses on the connected seller's own operational data. It does not claim access to market-wide competitor intelligence.
SKU and ASIN
Used to identify and relate the seller's listing records inside the tenant workspace.
Price and availability
Known listing price, quantity and status support basic operational review.
Cost assumptions
Users provide their own cost inputs for scenario analysis. OmniSeller does not silently infer missing costs.
Fit before access
Have a specific operating question?
Describe it before connecting an account. We will tell you whether the current beta has the data and workflow to answer it.