Amazon PPC software features

Detailed capabilities, honest status, and clear control boundaries.

Review what SellerPilot supports today, what is being built, and what cannot be enabled until Amazon access and safety requirements are satisfied. Every section distinguishes read-only analysis from proposed or live campaign changes.

Start 15-day trial See the status matrix

Available now

Amazon PPC analytics and reporting

Bring authorized advertising profiles, campaign structure, and performance reports into one organization-scoped workspace.

Spend, attributed sales, orders, impressions, clicks, ACOS, ROAS, CTR, and conversion rate
Date-range and advertiser-profile filters
Profile-level currency handling
Visible data-through and last-sync timestamps
Deterministic summaries generated from synchronized reports
Empty and incomplete-data states that do not invent performance

Analytics are only as reliable as their scope. SellerPilot keeps the selected profile, reporting window, currency, and freshness visible so a customer can reproduce the calculation. It does not silently merge incompatible currencies or represent a delayed report as final.

Available now

Budget pacing and spend control

Compare accumulated spend with the elapsed portion of the period instead of relying on a simple daily average.

Spend-to-date versus time-elapsed comparison
Projected pacing state with clear assumptions
Campaign budget visibility
Overspend and underspend attention states
No campaign write access in the current phase
Profile and currency context retained

Budget pacing helps teams notice risk early, but it is not a guarantee of delivery or sales. Demand, eligibility, inventory, Buy Box status, competition, and Amazon serving behavior can all affect spend. SellerPilot presents pacing as decision support, not a promised outcome.

In development

Wasted-spend and target review

Surface campaigns, targets, placements, and search terms that deserve review while keeping the evidence attached.

Configurable evaluation windows
Clicks, spend, orders, and attributed sales evidence
Target ACOS or ROAS context
Search-term and target-level review
Launch and learning-period exceptions
No automatic negative targeting until approved

A zero-order target is not automatically wasteful. The data window, click volume, product lifecycle, attribution delay, margin, and campaign objective matter. Planned review logic will expose those inputs rather than label activity with an unexplained score.

Available now

Explainable PPC recommendations

Turn account observations into reviewable proposals instead of opaque commands.

Current and proposed value
Evidence window and supporting metrics
Reason, expected direction, and uncertainty
Affected account, campaign, ad group, or target
Permission and budget validation
Customer approval state

A recommendation is never described as an executed action. SellerPilot preserves the boundary between source data, calculated evidence, proposed change, and customer decision. Amazon execution is disabled, and recommendations do not guarantee sales, ranking, ACOS, ROAS, or profit.

Available now

Approval records and action history

Record who reviewed a proposal, the evidence they saw, and the decision they made without implying Amazon execution.

Role-checked approval requests
Versioned evidence snapshots
Approve or reject decisions with reasons
Idempotent decision records
Immutable append-only history
Approval never triggers an Amazon write

Approval records operate inside the organization and preserve the reviewed evidence and proposed change. Database controls prevent rewriting decisions or history. Execution remains a separate, unavailable capability and would require additional Amazon access, precondition checks, and safety certification.

In development

Multi-account and agency operations

Keep organizations and connected advertising accounts isolated while giving authorized teams a consistent workflow.

One, three, or ten connected-account plan limits
Organization and tenant isolation
Account switcher and profile filtering
Role-based access design
Account-level sync and freshness status
Activity history and accountable ownership

SellerPilot pricing uses connected Amazon accounts as the plan limit, while advertiser profiles may exist beneath an authorized account. Final account counting and edge cases will be documented before commercial launch so agencies can predict billing accurately.

Available now

Connection security and operational trust

Protect credentials and customer data with server-side controls designed for a multi-tenant business application.

Amazon OAuth authorization
Encrypted refresh credentials
No Amazon passwords collected
Tenant-scoped database access patterns
Rate limits and session controls
Safe error messages and sync audit state

Security is a continuing operational obligation, not a page claim. SellerPilot's public policies describe authorized use, retention, deletion, incident reporting, and customer rights. Production launch remains dependent on completing operational reviews and required provider configuration.

Research stage

Customer-authorized AI and MCP review

A planned conversational layer may let customers ask structured questions about their workspace through supported assistants.

Explicit customer connection and scope
Read-only tools before any action tools
Organization and role checks
Minimal fields returned per question
Provider disclosure and revocation
No third-party transfer without authorization

This is not currently a live product feature. Amazon policy restricts sharing or combining Amazon data with third parties without authorization. SellerPilot will not market an AI account-review connection as available until the legal, policy, security, provider, and customer-consent requirements are satisfied.

Availability matrix

Can you use it now, and is it part of the roadmap?

“Roadmap” means intended direction, not a release commitment. Amazon access, technical validation, security review, and marketplace eligibility can change the final scope.

Capability	Available now	Roadmap	Important condition
Secure Amazon authorization	Yes	Yes	Amazon-hosted OAuth; no password collection
Profile and campaign synchronization	Yes	Yes	Authorized read scopes and configured regions
Performance dashboard	Yes	Yes	Depends on completed reporting jobs
Budget pacing	Yes	Yes	Decision support; no spend guarantee
Wasted-spend review	No	Yes	In development
Explainable recommendation queue	Yes	Yes	Read-only proposals from synchronized evidence
Approval decisions and immutable history	Yes	Yes	Records decisions; does not execute changes
Customer-approved write actions	No	Yes	Amazon approval and validation required
Autonomous optimization	No	No	Not offered; future scope would require separate review
External AI/MCP account review	No	Yes	Research stage and approval-dependent

Permanent guardrails

Controls that should remain true as the platform expands.

No credential collection

Amazon passwords are never a SellerPilot input. Authorization uses Amazon's supported flow.

No invented performance

Empty, delayed, or incompatible datasets are labeled instead of replaced with sample business results.

No invisible action

Any future write action must preserve the proposal, customer decision, submitted request, and confirmed outcome.

No guaranteed results

Advertising outcomes depend on factors outside SellerPilot. Insights and projections remain decision support.

Feature questions

How should teams evaluate these capabilities?

Why show features that are not live?

Customers need to understand the intended platform direction, but roadmap items must not be confused with current service. Each planned capability is labeled beside its operational dependencies.

Will every marketplace support every feature?

Not necessarily. Amazon API coverage, advertising products, account eligibility, reporting, and permissions can vary. SellerPilot will document marketplace support feature by feature after validation.

Are approved recommendations changing bids?

Not by approval alone. The controlled execution path is limited to reversible keyword bids and remains locked until production access, platform and tenant safety gates, fresh data, numeric limits, reconciliation, and rollback protections all pass.

Is competitor intelligence a customer data source?

No. External keyword and competitor research supports SellerPilot's own marketing. It is not a source of customer Amazon advertising data, campaign performance, or optimization decisions.

Choose the right starting point

Begin with transparent reporting and budget visibility.

Review the platform design, compare account limits, and start the trial only when the current capability set matches your needs.

Start 15-day trial Explore the platform View pricing