Frequently asked questions

Terra PPC is advertising analytics, seller-business intelligence, economics, and controlled automation software for Amazon sellers, brands, and agencies. It is designed to organize authorized advertising data, analyze PPC performance, read selected seller-business context where authorized, model profitability from customer-configured product economics, and run rule-based automation in Manual, Review or Auto mode with guardrails and an audit history.

Terra PPC is a software product operated by ĐT ORGANIC COMPANY LIMITED, a company based in Vietnam. ĐT ORGANIC COMPANY LIMITED is responsible for the website, the service and the handling of data described in the Privacy Policy.

ĐT ORGANIC COMPANY LIMITED is the registered foreign-language name of CÔNG TY TNHH ĐT ORGANIC (Enterprise Registration No. 5901217159). Terra PPC is a product and brand of that company, not a separate legal entity. Registered address: 02/34/61 Lu Gia, Thong Nhat Ward, Gia Lai Province, Vietnam. Contact: admin@terrappc.com. The full legal identity is on the About page.

Amazon sellers, Amazon brands, in-house advertising teams, and agencies that manage advertising for client accounts they are authorized to access.

Advertising workflows: campaign, ad group, keyword, target and search-term analysis; bid, budget and placement workflows; recommendations; controlled automation; and advertising reporting.

Seller-business workflows, where authorized: sales and traffic, finance and settlements, FBA inventory, listings and product context, marketplace insights and brand or retail analytics that help explain advertising results and profitability. See Business Intelligence.

Economics workflows: customer-configured COGS and landed cost, cost history, FIFO layers, price history, returns, indirect expenses, modeled P&L and break-even thresholds. See Economics & Profitability.

Not through self-serve sign-up. Access is arranged through a request and a quote. Submitting an inquiry through the contact form does not create an account or a paid subscription.

No. Terra PPC does not ask customers to provide their Amazon password directly to Terra PPC. Supported Amazon account connections are designed around Amazon-provided authorization mechanisms rather than collection of Amazon account passwords.

Terra PPC also never asks for a Seller Central or advertising console password, or for a multi-factor authentication code.

Advertising data comes from the Amazon Ads API and describes advertising: campaigns, ad groups, keywords, targets, search terms, bids, budgets, placements and performance reporting.

Seller-business data comes from the Selling Partner API (SP-API), where authorized: marketplace participation, aggregated sales and orders, financial transactions and fees, FBA inventory, listings and, where available, Brand Analytics reports — subject to the roles Amazon approves.

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

No. Terra PPC is an independent software product operated by ĐT ORGANIC COMPANY LIMITED. It is not affiliated with or endorsed by Amazon. References to Amazon describe intended platform compatibility.

Terra PPC is designed for authorized Amazon advertising and seller workflows. 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 website describes how those connections are designed. It does not state that any specific Amazon approval has been granted.

No. Current analytics-oriented use cases are designed without requiring buyer contact or shipping information. Terra PPC is not designed to use buyer names, addresses, email addresses or phone numbers, and its current functionality does not call for Amazon roles that provide buyer personally identifiable information.

Yes. Authorization can be revoked through the applicable Amazon account settings. You can also ask Terra PPC to disconnect an account and delete associated data through the data deletion process.

Advertising metrics show what ads are doing; seller-business context explains what is happening around them. Total seller revenue is needed for TACoS, actual fees and refunds for modeled profitability, and inventory and listing status to decide whether scaling an ad is safe.

Seller context is used only where the customer authorizes it and only for enabled functionality. See Business Intelligence.

No. They represent separate authorization and scope contexts. Advertising access is authorized for the Amazon Ads API; seller-business access is authorized separately through the Selling Partner API. Each can be revoked on its own.

Where authorized, financial transactions: product charges with their referral and FBA fee components, storage and other fees, refunds, promotions, reimbursements and fee adjustments, grouped into settlement periods with released and deferred amounts.

It supports historical profitability and reconciliation. Records carry amounts, types and SKUs — not buyer names, addresses, emails or phone numbers. Fee estimates are kept separate and are never added to actual fees.

It shows fulfillable, inbound, reserved, unfulfillable and researching units and the days of cover at recent sales velocity.

Where authorized, the Inventory Guard holds advertising scale actions — such as bid or budget increases — for a product that would run short of stock. It never pauses advertising on its own, and every held action is recorded.

Total advertising cost of sales: Ad Spend ÷ Seller Gross Revenue × 100. Unlike ACoS, which divides by ad-attributed sales only, TACoS compares advertising spend with all seller revenue.

Terra PPC uses this one definition everywhere. In the demo account, $2,049.54 of ad spend against $21,430.00 of seller gross revenue gives a TACoS of 9.6%. When seller revenue is unavailable, TACoS is shown as unavailable — never as zero.

Because an ACoS is only good or bad relative to what a product can afford. COGS, together with Amazon fees, other variable costs and refunds, sets the contribution each sale leaves for advertising — and therefore the modeled break-even ACoS every campaign is measured against.

When a supplier raises the unit cost, break-even falls the day the new cost applies, and the business guards can hold scale actions that would now lose money. See Economics & Profitability.

No. COGS, landed cost components such as freight, duty and packaging, and other non-Amazon business costs are configured by the customer. They are not assumed to be supplied by Amazon, and wherever they appear they are labelled as an assumption.

First in, first out: each purchase layer keeps the units it still holds and its unit cost, and sales use the oldest layer first. A newer, more expensive layer changes nothing until its units start selling, and one day's sales can cross two layers.

FIFO is one of six costing methods a product can use; the others are constant, period-based, batch-based, weighted average and marketplace-specific. See FIFO cost layers.

Seller revenue less refunds, Amazon fees, COGS, ad spend and other costs, plus reimbursements — each line with its source. Terra PPC shows contribution before ads, modeled net profit and fully allocated profit after indirect expenses.

It is a model built from authorized data and customer-configured costs. It is not GAAP profit, accounting net income or taxable profit.

The ACoS at which modeled profit after ads reaches zero. For a campaign it equals the pre-ad contribution margin of the products it sells, weighted by their ad-attributed sales. A campaign above its break-even loses modeled money on each ad-attributed sale.

A suggested Target ACoS ceiling sits below break-even, moved by the desired margin you configure.

The most a click can cost before an ad-attributed sale stops covering its contribution: ad-attributed revenue per click × pre-ad contribution margin. It is economics context, not an auction prediction.

Break-even CPC is planned. It exists in Terra PPC's economics engine but is not yet shown in the interactive demo.

Unavailable is not zero. When a source is not authorized or not available, Terra PPC marks the result instead of filling the gap: without finance data profitability is partial, without seller revenue TACoS is unavailable, and without inventory data the Inventory Guard is not evaluated — never treated as a pass.

You define a rule with conditions (for example, ACoS above a configured target with at least a minimum number of clicks), an action (such as a bid adjustment) and guardrails (bid floor, bid ceiling, maximum change per cycle, cooldown).

Rules are grouped into strategies. Each automation cycle follows the execution planner's fixed order: authorization, scope and data readiness first, then safety, the proposals, conflict resolution and the guardrails, and only then the mode you chose. Important recommendations and actions are designed to be recorded in an audit history. See Automation.

Manual: you control actions directly. Automation can be inspected or simulated but does not apply operational changes.

Review: rules evaluate conditions and Terra PPC creates recommendations that a user approves or rejects before anything executes.

Auto: eligible rule actions may execute automatically within configured scope, permissions and guardrails, and are recorded for review.

No mode bypasses account authorization, scope, guardrails, permissions or audit logging. Terra PPC is designed so that an action outside the configured limits is not executed — it is blocked or routed to review instead.

Terra PPC is designed to resolve conflicts deterministically, so exactly one proposal per entity survives a cycle. Protective actions come first — pause, then negative, then bid, then budget, then informational. Within the same kind of action the higher rule priority proceeds, and at equal priority the more conservative value.

A business guard can still hold the surviving scale action. The suppressed proposal, the resolution and its reason are recorded.

The part of Terra PPC that decides what should be considered or proposed. It evaluates scoped performance, business context, economics, rules, strategies and data readiness before producing a recommendation or an eligible operational proposal — deterministically, with a reason for every result; no machine learning is involved. See Decision engine.

The fixed order of one automation cycle — 18 steps from scope validation and data readiness, through the circuit breaker, inventory, listing and margin safety, the proposals in stage order, the conflict resolver and the global guardrails, to the mode, the action and the audit record. The decision engine asks what should be proposed; the execution planner asks whether it can proceed safely and in what order. See Execution planner.

Global guardrails limit every automatic change: bid floors and ceilings, maximum change per cycle, cooldowns and actions per campaign. Business-aware guards — Inventory, Listing, Cost Increase, Break-even and Financial Margin — hold scale actions when the business context says scaling is unsafe; they never pause advertising. Refund review is advisory.

Emergency controls can stop increases for a whole scope, and the circuit breaker routes Auto actions to review when a cycle would exceed its limits. See Business-aware guardrails.

Terra PPC AI/MCP is Terra PPC's own interaction layer for AI-assisted workflows. It is designed to let compatible AI clients ask questions, retrieve scoped context, prepare recommendations and — where permitted — request guarded actions through the same authentication, authorization, scope, policy and mode controls as the rest of the product. See AI & MCP.

No. The Amazon Ads MCP Server is Amazon's technology. Amazon Ads has announced it as a way for AI agents to work with Amazon Ads API functionality, with availability subject to Amazon Ads eligibility, credentials, authorization and applicable terms.

Terra PPC AI/MCP is a separate product layer operated by ĐT ORGANIC COMPANY LIMITED.

No. By design, AI clients do not receive unrestricted database access, customer passwords or cross-customer context. They receive scoped context for the selected organization, account, profile and marketplace, and any action request still passes policy, mode and guardrail checks.

An AI-assisted request is handled like any other: it is authenticated, authorized and scoped, and any change it proposes passes the same decision engine, execution planner, guardrails and mode. In Manual and Review modes it produces previews or recommendations; in Auto mode only eligible actions within guardrails can execute. AI-assisted workflows do not bypass automation modes, permissions or safeguards.

Terra PPC is designed around authorized access, least privilege, account scoping, data minimization, secure transport and traceability. Amazon-related data is used only for authorized product functionality, is accessed on a need-to-know basis, and is not published or sold. See the Security Overview.

No. Terra PPC does not sell, resell or publicly publish customer Amazon data, and does not offer it as a standalone dataset. Authorized data is used to provide the functionality the customer has enabled.

Use the security reporting page. Describe the issue, the affected URL or function, safe reproduction details and the potential impact. Please do not access other customers' data, run destructive tests or disrupt the service.

Terra PPC does not currently hold or claim third-party security certifications. Its security approach is described as design principles and controls on the Security Overview. Certifications will be listed only once they exist and can be verified.

Submit a request through the data deletion page or the contact form with the Data Deletion topic. Terra PPC may verify your authority over the account, reviews the scope of the request, and deletes or de-identifies eligible data according to applicable requirements. Limited records may be kept where required by law or for security and dispute purposes.

No. The Terra PPC public website does not use analytics cookies, advertising pixels or third-party trackers. The Privacy Policy explains the technical information our hosting provider processes to deliver and protect the site.

It is delivered to Terra PPC by email so we can respond. It is used to answer your inquiry and manage any resulting business relationship — not for advertising — and it is kept only as long as needed for those purposes.

Pricing is quote-based. It depends on connected advertising accounts, marketplace coverage, enabled modules, expected reporting and automation usage, AI/MCP functionality where enabled, and support and onboarding requirements. See Pricing.

No. Terra PPC software pricing is separate from advertising spend and any applicable third-party or platform charges. Advertising costs are billed by Amazon under your advertising account.

No. Requesting access or a quote costs nothing and does not create a paid subscription.