Orbit Methodology: Inputs, Decisions, and Human Controls
Quick answer: Orbit connects Amazon advertising, search, conversion, inventory, and product economics so approved decisions can be executed consistently. A senior operator defines the objective, rules, thresholds, protected areas, and approval mode. Orbit applies permitted actions, records what changed, and escalates exceptions. It does not replace accountable management.
Scope: This page documents Eva Commerce’s public operating method for Orbit. Available inputs and actions depend on account permissions, data quality, marketplace support, product configuration, and the service scope approved with the brand.
Why Orbit exists
Amazon advertising decisions do not happen in isolation. A bid can influence traffic and sales, but its value depends on conversion, organic visibility, stock coverage, price, margin, product maturity, and the campaign’s job. When those signals live in separate reports, teams react late or optimize a media metric while the product economics move in the opposite direction.
Orbit is designed to turn an operator’s strategy into explicit decision policy. The point is not to remove people. The point is to let experienced people apply a coherent strategy across more products and respond while the evidence is still useful.
The Orbit decision loop
| Stage | What happens | Human responsibility |
|---|---|---|
| 1. Define | The brand and operator establish objectives, product roles, economic inputs, thresholds, and exclusions | Approve the business policy and source data |
| 2. Observe | Orbit reads authorized advertising and commerce signals | Confirm access, freshness, and known gaps |
| 3. Evaluate | Signals are assessed against the approved policy for each product and campaign | Define how conflicts and uncertainty are handled |
| 4. Act | Orbit reports, proposes, or executes a permitted decision based on the control mode | Choose the approval mode and action limits |
| 5. Record | The prior state, signal, rule, action, and time are retained | Review material changes and exceptions |
| 6. Learn | Results and operating changes inform the next review | Update strategy when the business context changes |
Inputs Orbit can use
The useful input set depends on the account and agreed scope. Orbit can combine the following categories when the data is available and authorized:
- Advertising: campaign, ad group, target, search term, placement, bid, budget, spend, attributed order, and attributed sales signals.
- Search: paid and organic query visibility, keyword coverage, rank movement, and search-term evidence.
- Conversion and retail readiness: traffic, conversion, offer state, content status, price, reviews, and identified catalog constraints.
- Inventory: available units, days or weeks of cover, lead time, inbound stock, stockout risk, and aged-inventory considerations.
- Product economics: approved price, product cost, marketplace and fulfillment costs, discount, return assumptions, and contribution thresholds.
- Business context: launch, growth, defense, harvest, clearance, seasonality, protected terms, priority products, and channel role.
Orbit cannot make an absent or incorrect input true. The operator must know which data is direct, estimated, delayed, or unavailable. Economic outputs are only as reliable as the brand-approved inputs behind them.
Decision classes
| Decision class | Examples | Control expectation |
|---|---|---|
| Bid and budget | Increase, reduce, cap, reallocate, or pause within approved bounds | Product objective, economic boundary, inventory state, and audit record |
| Search-term control | Promote proven queries, isolate terms, propose or apply negatives | Evidence threshold, protected-term list, and exception path |
| Coverage | Identify missing product, category, competitor, or branded demand | Retail readiness and operator approval before expansion |
| Inventory response | Throttle spend, protect rank, or flag a conflict | Approved coverage thresholds and named operations owner |
| Profit response | Surface cases where attributed growth conflicts with contribution | Approved cost inputs, objective, and human resolution |
| Exception management | Flag conflicting signals, missing data, unusual movement, or policy limits | No silent action outside the permitted policy |
Human control modes
- Observe: Orbit reports the decision and evidence without changing the account.
- Recommend: Orbit proposes an action for operator approval.
- Execute within policy: Orbit applies actions that fall inside the approved rules and limits.
- Escalate: Orbit routes missing data, conflicts, or out-of-policy situations to a named operator.
The mode can differ by product, campaign, decision type, and operating stage. A mature replenishable product may permit more execution than a launch, a protected brand term, a constrained product, or an unusual event.
What the audit trail should answer
- What changed?
- What was the prior state?
- Which signal and rule supported the change?
- When did it happen?
- Was it observed, recommended, approved, or executed automatically?
- Who owns the policy and the exception?
- What data was missing, stale, or estimated?
Three illustrative examples
Inventory constraint: A product falls below its approved days-of-cover threshold. Orbit reduces or proposes reducing eligible spend, depending on the control mode, and records the inventory signal. The operator decides whether rank protection or another business priority justifies an exception.
Search-term decision: A query reaches the required evidence threshold without the approved outcome. Orbit can recommend or apply a negative under the policy. Protected discovery terms and strategic campaigns remain outside that action unless the operator changes the rule.
Contribution conflict: Attributed revenue grows while product contribution falls below the approved boundary. Orbit surfaces the conflict and the inputs behind it. The operator determines whether the brand is intentionally investing in launch, rank, or customer acquisition, or whether spend should move.
What Orbit does not claim
- Orbit does not guarantee revenue, rank, profit, or any other outcome.
- Orbit does not turn incomplete product costs into audited financial statements.
- Orbit does not replace legal, compliance, finance, product, or executive approval.
- Orbit does not make every Amazon signal available in real time.
- Orbit does not remove the need for creative, catalog, inventory, pricing, and operations work.
- Orbit does not execute outside the access and control policy approved for the account.
How to evaluate Orbit in a brand account
- Choose one product group and document its objective, economics, inventory, and constraints.
- Confirm every required input and label estimates or missing data.
- Review the proposed rules, thresholds, protected areas, and control mode.
- Trace sample decisions from signal through policy, action, and record.
- Define exception ownership and the review cadence.
- Compare the resulting decisions with the brand’s prior process using the same period and definitions.