Skip to main content
B
BFarm
// Client-scoped Amazon analytics reporting

BFarm Insights

Last Updated: August 10, 2026

Turn Amazon analytics exports supplied directly by your team into a structured, read-only reporting view. A narrow Public SP-API connection is planned only after Amazon approval and production security verification.

Product questions go to max@bfarm.top.

Discuss BFarm InsightsDeveloper information
BFarm Insights app icon

Available today

Managed reporting from client-provided exports

Available today through Amazon analytics exports supplied directly by the managed-service client, with client-scoped storage and read-only reporting.

  • Each source file must come directly from the client authorized to share it.
  • Files, calculations, and reports remain isolated to that client's written service scope.
  • Reporting records the source period, material assumptions, and freshness.
  • Human-reviewed reports support decisions and do not publish changes to Seller Central.

Planned after Amazon approval

One role and two read-only reports

Planned only after the required Amazon approval, production implementation, security verification, and seller authorization.

Planned SP-API role: Brand Analytics

BFarm currently has no approved or active SP-API application or production OAuth integration.

Data and capability boundary

ReportAvailable todayPlanned API accessEligibility
Search Query Performance (SQP)Client-provided exportRead-only API requestAvailable only to eligible Brand Registry sellers.
Sales and TrafficClient-provided export when included in the service scopeRead-only API requestAvailable to eligible seller accounts.

Not accessed or planned in this release

The following are excluded from the planned SP-API integration. They describe the requested API scope, not the existing managed service, which is described in the Privacy Policy.

  • Buyer names, addresses, phone numbers, communications, and other buyer PII
  • Seller Central passwords, private applications, Client IDs, Client Secrets, refresh tokens, and other client API credentials
  • Orders, Listings, Pricing, Finance, FBA, and Amazon Ads API data
  • Listing, pricing, advertising, or other write operations
  • Use of Amazon Information to train, fine-tune, or evaluate any model
  • Automated or model-initiated action on a seller account without operator review and seller approval
  • External Amazon-derived datasets, resale of Amazon data access, and cross-seller pooling or aggregation

Future seller authorization flow

This flow is descriptive only. No authorization entry point is available before the required approval, implementation, and production acceptance.

  1. STEP 1BFarm obtains the required Amazon approval and its own Login with Amazon credentials.
  2. STEP 2The seller opens a BFarm connection link and continues to Amazon.
  3. STEP 3Amazon presents the approved Brand Analytics permission for seller consent.
  4. STEP 4Amazon returns a short-lived authorization code to the BFarm server-side callback.
  5. STEP 5BFarm exchanges the code server-side and binds the authorization to the correct seller and client scope.
  6. STEP 6The seller can revoke access through Amazon; BFarm will also provide a disconnect path before activation.

Amazon Ads API remains a separate future integration with its own Amazon authorization; it is not included in the planned Brand Analytics SP-API grant.

Managed-service pricing

Included in eligible BFarm managed-service retainers starting at USD 1,000 per month. No standalone software subscription today. Exact scope is defined in the service agreement.

Discuss BFarm InsightsPrivacy PolicySP-API compliance

Your privacy choices

Optional analytics only after you accept.

BFarm uses optional analytics and advertising technologies only after you accept. Rejecting does not affect the website or forms. See the Privacy Policy.