Skip to content

Lynx internal operations platform

Connected operations without password sharing.

Lynx uses internal tools to turn seller-authorized Amazon reports and operational data into review queues, alerts, and accountable actions. Access is role-based, limited to the contracted scope, and removable by the seller.

Amazon Information originates only through Seller Central, Amazon Ads, SP-API, and Amazon-generated reports. Hosting and database providers operate as controlled subprocessors, not as external sources of Amazon Information.

01

Seller authorization

The seller grants Lynx approved roles through Amazon's supported authorization workflow.

02

Scoped connection

Only data required for the contracted modules is accessed. Standard agency workflows do not require restricted buyer PII.

03

Reviewed action

Tools surface recommendations and work queues. Material account changes follow the approved operating process.

Internal modules

The platform is used by approved Lynx operators within client engagements. The public tools on this website remain browser-based and do not connect to Seller Central.

Seller-provided commercial inputs, such as product costs and creative assets, remain separate from Amazon Information and are used only for the agreed client work.

01

Account health monitor

Surfaces operational alerts, listing risks, and assigned follow-up actions.

Data scope: Account and catalogue status

02

Catalogue health workspace

Tracks listing completeness, suppression risks, variations, and approved changes.

Data scope: Product Listing and catalogue data

03

Profit-leak dashboard

Combines settlements, fees, advertising, and seller-provided COGS for SKU-level analysis.

Data scope: Finance reports and advertising summaries

04

Search-term operating queue

Turns search-term reporting into reviewed negative, harvest, and bid actions.

Data scope: Advertising performance data

05

Inventory risk monitor

Flags coverage, inbound, stranded, and stockout risks for operator review.

Data scope: Inventory and fulfilment reporting

06

Performance reporting

Produces client-facing weekly and monthly views with an auditable action history.

Data scope: Aggregated sales and operational metrics

Least-privilege access

Requested scopes and why they are needed

Amazon determines role eligibility and sellers choose which approved roles to grant. This table describes Lynx's expected business need; it does not represent automatic or unrestricted access.

ScopeModeBusiness purpose
Product ListingView and editCreate and maintain listings, attributes, variations, and approved content changes.
Inventory and Order TrackingView, limited edit where requiredMonitor inventory, fulfilment status, and aggregated sales performance without shipment PII.
PricingView and approved editSupport launch pricing, promotions, and seller-approved offer updates.
Finance and AccountingViewReconcile settlements, Amazon fees, refunds, and contribution margin.
Selling Partner Insights and Brand AnalyticsViewMeasure search, traffic, conversion, and brand performance using aggregated data.
Amazon FulfilmentView and limited operational editMonitor FBA inventory and inbound issues within the contracted operations scope.
Amazon AdvertisingView and editBuild and optimize seller-approved advertising campaigns through Amazon Ads access.

What we do not request by default

  • Buyer shipment PII: standard catalogue, advertising, finance, and inventory analytics do not require buyer names, addresses, or contact details.
  • Payment initiation: Lynx does not initiate seller payouts or buyer refunds through a payment-provider role.
  • Unrestricted administration: account-owner functions and seller employee-only roles remain with the seller.
  • Credentials: sellers do not provide passwords, MFA codes, or secret keys to Lynx personnel.

Connect only after the scope is clear.

The audit defines the work, the required roles, and the data boundaries before authorization begins.

Request an access review
Book my free Amazon audit