Skip to main content
Terra PPC
Terra PPC

Designed for authorized Amazon advertising and seller workflows.

Terra PPC is designed to work with two Amazon interfaces for two different jobs: the Amazon Ads API for advertising workflows, and the Selling Partner API (SP-API) for selected seller-business context. Each is used only with the customer's authorization and for the functionality it supports. Product costs are configured by the customer, and metrics such as TACoS and break-even are derived by Terra PPC.

Open Reviewer GuideRequest Access

Two authorization planes.

Advertising and seller-business connections represent separate authorization and scope contexts. They are granted separately, scoped separately and revoked separately — access to one does not grant access to the other.

  • Amazon Ads API: advertising accounts and profiles
  • SP-API: a selling partner and its marketplaces
  • Terra PPC never asks for an Amazon password
Conceptual authorization model. The customer grants two separate authorizations on Amazon: advertising authorization through Amazon-provided consent for the Amazon Ads API, which covers an advertising account or profile, and seller authorization through SP-API OAuth, which covers a selling partner and marketplace. Access to one does not grant access to the other. Terra PPC scoped services use each connection only for the functionality it authorizes. No Amazon password is entered into Terra PPC.

ConceptualConceptual architecture. No Amazon login screen is shown or imitated.

Amazon advertising workflows

Why Terra PPC asks for advertising access: eight workflows, each backed by a product capability you can test in the interactive demo.

Designed for the Amazon Ads API, subject to approved access, credentials, and authorization.

Hourly advertising context

Designed to support hourly advertising workflows where the applicable Amazon advertising integrations are available.

ADS HOURLY: hour-of-day advertising data (Amazon advertising context; a synthetic hourly model in the demo) The interactive demo uses a synthetic hourly model, not a live data stream.

  • Hourly performance

    Hour-of-day spend, clicks, orders and sales for each campaign.

    In Terra PPC: Hourly Optimization

    Hourly Optimization demo

  • Budget consumption

    How much of the daily budget is used by each hour.

    In Terra PPC: Hourly Optimization · Budget Planning & Pacing

    Hourly Optimization demoBudget Planning & Pacing demo

  • Hourly optimization

    Schedule proposals for weak and strong hours, following the campaign's mode.

    In Terra PPC: Hourly Optimization

    Hourly Optimization demo

  • Dayparting context

    Hour-of-week schedules of bid adjustments and pauses.

    In Terra PPC: Dayparting

    Dayparting demo

What each interface is designed to cover

Two data planes, each tied to its own purpose. Examples describe intended functionality, not granted access.

Advertising

Amazon Ads API — subject to approval, credentials and authorization.

Designed to cover

  • Campaign analytics
  • Ad group reporting
  • Keyword analysis
  • Target analysis
  • Search terms
  • Bid workflows
  • Budget workflows
  • Placement context
  • Advertising reporting
  • Controlled automation

Used for

Advertising analytics, recommendations and controlled automation — every change follows the customer's mode and guardrails.

Authorization

Advertisers authorize access through Login with Amazon, Amazon's OAuth-based consent. Terra PPC then works only with the advertising profiles that were authorized.

See it in the interactive demo

Seller business context

Selling Partner API (SP-API) — subject to approved roles, authorization and enabled functionality.

Designed to cover

  • Marketplace participation
  • Seller sales
  • Sales & Traffic
  • Financial transactions
  • Fees / refunds
  • FBA inventory
  • Listings / catalog
  • Retail / search analytics

Used for

Explaining advertising results, modeling profitability and holding unsafe scale actions — with selected, non-PII seller-business context.

Authorization

Public SP-API connections are designed to use Amazon-provided OAuth authorization: the selling partner approves Terra PPC through Amazon's authorization workflow, separately from advertising access.

See it in the interactive demo

Seller-business context use cases

Why Terra PPC asks for seller-business context: advertising results are read next to sales, finance, inventory, listings and retail context — where authorized, and without buyer personal information.

Selling Partner API (SP-API) — subject to approved roles, authorization and enabled functionality.

Intended SP-API capability areas

Each area supports one real Terra PPC feature, one workflow and one data need. Areas without a product purpose are not requested.

Actual roles, operations, marketplace availability and access remain subject to Amazon approval, authorization, current role mappings, and enabled Terra PPC functionality.

  • Intended capability area

    Selling Partner Insights

    Purpose
    Marketplace context
    Data
    Marketplace participation and seller-performance context used to scope every view to the right marketplace.

    No buyer PIIDemo

  • Intended capability area

    Inventory and Order Tracking

    Purpose
    Aggregated business metrics
    Product feature
    Sales & Traffic
    Data
    Aggregated order and sales metrics — seller revenue, orders and units — without individual order or buyer detail.

    No buyer PIIDemo

  • Intended capability area

    Finance and Accounting

    Purpose
    Financial context
    Data
    Financial transactions, fees, refunds, adjustments, reimbursements and settlement context for historical profitability.

    No buyer PIIDemo

  • Intended capability area

    Amazon Fulfillment

    Purpose
    FBA context
    Data
    FBA inventory states — fulfillable, inbound, reserved, unfulfillable — used before scaling advertising.

    No buyer PIIDemo

  • Intended capability area

    Product Listing

    Purpose
    Listing context
    Data
    Listing status, catalog information and applicable fee-planning context at SKU level.

    No buyer PIIDemo

  • Intended capability area

    Brand Analytics

    Purpose
    Retail and search context
    Data
    Sales and traffic business reporting and search-query performance, where authorized and available.

    No buyer PIIDemo

  • Optional · not requested

    Pricing

    Considered only if Terra PPC adds pricing-aware analysis. It is not part of the current product or application.

Intended SP-API capability areas and the features they support: Selling Partner Insights: Marketplace context, used by Seller & Marketplace Insights; Inventory and Order Tracking: Aggregated business metrics, used by Sales & Traffic; Finance and Accounting: Financial context, used by Finance & Settlements · Profitability; Amazon Fulfillment: FBA context, used by Inventory & FBA · Inventory Guard; Product Listing: Listing context, used by Listings & Product Context; Brand Analytics: Retail and search context, used by Brand & Retail Analytics. Pricing is optional · not requested. Actual roles, operations, marketplace availability and access remain subject to Amazon approval, authorization, current role mappings, and enabled Terra PPC functionality.

Intended capability areas

Each area maps to one product feature and one demo page

  • Selling Partner Insights

    Marketplace context → Seller & Marketplace Insights

    /demo/seller-insights

  • Inventory and Order Tracking

    Aggregated business metrics → Sales & Traffic

    /demo/sales-traffic

  • Finance and Accounting

    Financial context → Finance & Settlements · Profitability

    /demo/finance

  • Amazon Fulfillment

    FBA context → Inventory & FBA · Inventory Guard

    /demo/inventory

  • Product Listing

    Listing context → Listings & Product Context

    /demo/listings-fees

  • Brand Analytics

    Retail and search context → Brand & Retail Analytics

    /demo/brand-analytics

  • Pricing Optional · not requested

Actual roles, operations, marketplace availability and access remain subject to Amazon approval, authorization, current role mappings, and enabled Terra PPC functionality.

Customer-configured data

These values are configured by the customer and are not assumed to be supplied by Amazon.

Labelled ASSUMPTION: customer-configured input, not provided by Amazon wherever they appear — COGS is never shown as seller or SP-API data.

How customer economics are used

  • COGS

    Product or manufacturing cost per unit, kept as dated cost versions per marketplace.

  • Freight

    International freight and inbound freight to FBA, on their own landed-cost lines.

  • Duty

    Import duty per unit, per marketplace.

  • Packaging

    Packaging, inspection, prep and labeling costs.

  • Other costs

    Other variable costs, the return policy and indirect expenses such as software or bookkeeping.

  • Desired margin

    The margin that sets a suggested Target ACoS ceiling below modeled break-even.

Terra PPC derived metrics

Calculated by Terra PPC from authorized advertising data, seller-business context and customer-configured economics. Each one names the sources it was calculated from.

Terra PPC derivedDERIVED: calculated by Terra PPC from the values shown

  • TACoS

    Ad Spend ÷ Seller Gross Revenue × 100 — unavailable, never zero, without seller revenue.

    See it in the demo

  • Break-even ACoS

    The pre-ad contribution margin of the products a campaign sells, weighted by their ad-attributed sales.

    See it in the demo

  • Break-even CPC

    Ad-attributed revenue per click × pre-ad contribution margin. Planned; not yet in the demo.

    Planned

  • Modeled Profit

    Seller revenue less refunds, Amazon fees, COGS, ad spend and other costs, plus reimbursements. Modeled, not accounting profit.

    See it in the demo

  • Inventory Risk

    Days of cover from FBA inventory states and recent sales velocity.

    See it in the demo

  • Profitability State

    A campaign's ACoS compared with its Target ACoS and its modeled break-even.

    See it in the demo

Integration matrix

Each product capability, the data context it reads, the integration family it is intended for, and where to see it working.

Actual roles, operations, marketplace availability and access remain subject to Amazon approval, authorization, current role mappings, and enabled Terra PPC functionality.

Request only what the product needs.

Terra PPC is designed around minimum necessary access. Current analytics-oriented use cases do not require buyer names, buyer email addresses, buyer phone numbers or buyer shipping addresses — and some things are never asked for at all.

  • Amazon account passwords, Seller Central passwords or advertising console passwords
  • Multi-factor authentication codes
  • Buyer names, addresses, email addresses or phone numbers for current functionality
  • Access to accounts, profiles or marketplaces the customer has not authorized
  • Unrestricted access to every Amazon API — only approved roles and scopes for enabled functionality
Least-privilege scope. Requested for enabled features: Advertising profiles, campaigns and performance reports; Marketplace participation; Aggregated seller sales and order metrics; Financial transactions, fees, refunds and settlements; FBA inventory states; Listing, catalog and fee-planning context; Brand Analytics reports, where available. Not requested: Buyer contact or shipping information — Analytics and automation do not need buyer names, emails, phone numbers or addresses. Buyer Solicitation — Terra PPC has no review or feedback solicitation feature. Buyer Communication — Terra PPC does not message buyers. Amazon Warehousing and Distribution — Terra PPC uses FBA inventory context only. Tax and restricted shipping roles — Terra PPC does not calculate taxes or ship orders.

Request only what is needed

Access is tied to enabled functionality

Requested for enabled features

  • Advertising profiles, campaigns and performance reports ADS: advertising data (Amazon Ads API context)
  • Marketplace participation SELLER: seller-business data (SP-API context, where authorized)
  • Aggregated seller sales and order metrics SELLER: seller-business data (SP-API context, where authorized)
  • Financial transactions, fees, refunds and settlements FINANCE: financial events (SP-API finance context, where authorized)
  • FBA inventory states SELLER: seller-business data (SP-API context, where authorized)
  • Listing, catalog and fee-planning context SELLER: seller-business data (SP-API context, where authorized)
  • Brand Analytics reports, where available SELLER: seller-business data (SP-API context, where authorized)

Not requested

  • Buyer contact or shipping information. Analytics and automation do not need buyer names, emails, phone numbers or addresses.
  • Buyer Solicitation. Terra PPC has no review or feedback solicitation feature.
  • Buyer Communication. Terra PPC does not message buyers.
  • Amazon Warehousing and Distribution. Terra PPC uses FBA inventory context only.
  • Tax and restricted shipping roles. Terra PPC does not calculate taxes or ship orders.

Combined decision architecture

Terra PPC uses authorized data only for approved functionality and applicable account context, subject to Amazon permissions and requirements.

Advertising context from the Amazon Ads API where authorized (campaigns, keywords, search terms, placements, spend, bids, budgets), seller business context from the Selling Partner API where authorized (seller sales, finance, inventory, listings, fulfillment, retail analytics) and customer-configured economics (COGS, freight, duty, packaging, other costs, desired margin) combine into the Terra PPC decision context for one scope, which supports analytics, recommendations, guardrails, auditability.

Availability depends on authorized integrations, approved access, enabled functionality, marketplace support, and applicable Amazon requirements.

Production availability of cross-source workflows depends on authorized integrations, approved functionality, applicable Amazon permissions, and enabled account scope.

Where to test each use case

The interactive demo runs every use case above on a synthetic account — no login, no Amazon data, and nothing is sent to Amazon. The Reviewer Guide walks through them in order.

Open Reviewer GuideLaunch Interactive Demo

Revoking access

Authorization belongs to the customer and can be withdrawn — each one on its own.

  • Revoking advertising authorization stops Terra PPC obtaining new advertising data through that connection.
  • Revoking seller authorization stops Terra PPC obtaining new seller-business data through that SP-API authorization.
  • Ask Terra PPC to disconnect an account through the contact form.
  • Request deletion of associated data through the data deletion process — a separate step.
Data DeletionContact Terra PPC

Integration status

Stated plainly, so nobody has to guess.

Use of the Amazon Ads API and the Selling Partner API is subject to Amazon's review and approval, active credentials and each customer's authorization. This page describes how Terra PPC's integrations are designed; it does not state that any specific approval has been granted.

Security OverviewPrivacy Policy

Terra PPC is independent of Amazon

Terra PPC is a software product operated by ĐT ORGANIC COMPANY LIMITED. It is not affiliated with or endorsed by Amazon. The Amazon Ads API and the Selling Partner API are Amazon technologies; references to them describe intended compatibility.

Request access to Terra PPC.

Tell us which accounts and marketplaces you manage and how much control you want to delegate. We'll follow up with access details and a quote.

Explore Interactive DemoRequest Access

Terra PPC is a software product operated by ĐT ORGANIC COMPANY LIMITED.

  1. Tell us about your accounts

    Advertising and seller accounts, marketplaces, and the workflows you want to control.

  2. We review scope

    Which modules, integrations and support your team needs.

  3. You receive a quote

    Access details and pricing, with no obligation to subscribe.