A 90-Day Plan for Detaching Ecommerce from Google Without Losing Sales

A documented analysis of the 90-day independence plan: risks, responsibilities, and practical steps for an ecommerce operation that is connected, but independent.

Published 22 September 202614 minutes

Editorial illustration about the 90-day independence plan and control of ecommerce infrastructure — One channel can accelerate sales without becoming the store’s central system.

The direct answer

UCP is worth analyzing as commercial infrastructure, not as just another new button. In the case of the 90-day independence plan, the difference between access and dependence appears in the technical and operational contracts. The concrete risk is that a sudden migration can sacrifice revenue, while delay perpetuates risk. The practical recommendation is simple: reduce dependence in stages, keeping profitable channels as adapters. That does not require withdrawing from Google. It requires Google to remain a channel connected to a commercial infrastructure that the store can operate without it.

What UCP is and what it does not solve

Universal Commerce Protocol is an open specification for exchanging commercial capabilities between agents, distribution surfaces, merchants and payment providers. The public documentation describes capability discovery, checkout and order management. UCP is not, however, a promise of traffic, a guarantee of eligibility, or an automatic transfer of the customer relationship. Technical implementation and access to a Google surface are separate decisions. A Romanian store can study the contract and prepare its architecture even if the commercial product is not available locally. It is precisely this separation that prevents investments made on the basis of a press headline.

The responsibility map

Layer	The control question	Minimum proof
Catalog	Who defines the product, variant and availability?	stable ID, version and readback
Offer	Who calculates the total and the commercial rules?	dated snapshot and expiry
Checkout	Where does the customer confirm and what do they see beforehand?	consent tied to the offer
Order	Who accepts, rejects and reconciles?	idempotency and auditable status
Relationship	Who can serve and win back the customer?	CRM, preferences and direct channel

In the case of the 90-day independence plan, the table must be completed with system names, owners and recovery times, not with marketing wording.

The catalog must remain the merchant’s source

Agents and feeds need structured data, but the source of truth should not be moved into an export. The internal catalog keeps the product identity, variants, units, restrictions and packaging rules; the adapter transforms this data for the channel. In the theme of the 90-day independence plan, this discipline makes it possible to stop or replace the integration without rebuilding the business. Validation includes price, currency, availability, taxes, delivery and expiry. If the feed and the internal system differ, the incident must be detected before a customer or agent creates an order based on an impossible offer.

1. Reconciliation lens: the decision for the 90-day independence plan

In the case of the 90-day independence plan, the lack of a definition for reconciliation shifts the discussion toward impressions and hides who bears the exception, loss or rule change. The pilot measures separately the effect on conversion, operating cost and the ability to resume the direct relationship. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. If we observe that a sudden migration can sacrifice revenue, while delay perpetuates risk, the pilot returns to the direct path. The team must reduce dependence in stages, keeping profitable channels as adapters, then repeat the test with the same products, markets and rules.

2. Margin lens: the decision for the 90-day independence plan

Seen through the margin lens, the 90-day independence plan is no longer an isolated function, but a decision about how value moves between store, customer and intermediary. The technical contract compares mandatory fields, intermediate states and the proof used when two systems disagree. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. This angle does not prove that the intermediary is useless; it proves that a sudden migration can sacrifice revenue, while delay perpetuates risk. For balance, the recommendation is to reduce dependence in stages, keeping profitable channels as adapters and to keep the channel only as long as it remains incremental.

3. Portability lens: the decision for the 90-day independence plan

For the 90-day independence plan, portability must be described before integration; otherwise the team will confuse a flow that works with a business it can control. The team documents the system that produces the information, the event that confirms it and the person who can correct an error. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. The exit criterion appears when a sudden migration can sacrifice revenue, while delay perpetuates risk. At that point we do not improvise a migration, but apply the documented decision: reduce dependence in stages, keeping profitable channels as adapters.

4. Identity lens: the decision for the 90-day independence plan

The identity test starts from the real operation associated with the 90-day independence plan, not from the commercial presentation of the protocol or platform. In a workshop, the process owner tests the normal path, then a timeout, a stock discrepancy and the removal of channel access. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. Here the risk is concrete: a sudden migration can sacrifice revenue, while delay perpetuates risk. That is why the measure cannot be only the number of orders. We add margin, recovery time and the percentage of cases resolved without manual export.

5. Consent lens: the decision for the 90-day independence plan

When we analyze the 90-day independence plan, the question about consent shows whether the advantage remains with the merchant after the session and campaign have ended. In the architecture register, the source, adapter, destination and the available alternative are versioned if the intermediary does not respond. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. The commercial consequence of the scenario is that a sudden migration can sacrifice revenue, while delay perpetuates risk. The verifiable answer remains: reduce dependence in stages, keeping profitable channels as adapters. The acceptance threshold is written before the test, not after the results are known.

6. Resilience lens: the decision for the 90-day independence plan

In the case of the 90-day independence plan, the lack of a definition for resilience shifts the discussion toward impressions and hides who bears the exception, loss or rule change. The pilot separates the effect on conversion, operating cost and the ability to resume the direct relationship. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. If we observe that a sudden migration can sacrifice revenue, while delay perpetuates risk, the pilot returns to the direct path. The team must reduce dependence in stages, keeping profitable channels as adapters, then repeat the test with the same products, markets and rules.

7. Continuity lens: the decision for the 90-day independence plan

Seen through the continuity lens, the 90-day independence plan is no longer an isolated function, but a decision about how value moves between store, customer and intermediary. The technical contract isolates mandatory fields, intermediate states and the proof used when two systems disagree. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. This angle does not prove that the intermediary is useless; it proves that a sudden migration can sacrifice revenue, while delay perpetuates risk. For balance, the recommendation is to reduce dependence in stages, keeping profitable channels as adapters and to keep the channel only as long as it remains incremental.

8. Observability lens: the decision for the 90-day independence plan

For the 90-day independence plan, observability must be described before integration; otherwise the team will confuse a flow that works with a business it can control. The team reconciles the system that produces the information, the event that confirms it and the person who can correct an error. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. The exit criterion appears when a sudden migration can sacrifice revenue, while delay perpetuates risk. At that point we do not improvise a migration, but apply the documented decision: reduce dependence in stages, keeping profitable channels as adapters.

9. Attribution lens: the decision for the 90-day independence plan

The attribution test starts from the real operation associated with the 90-day independence plan, not from the commercial presentation of the protocol or platform. In a workshop, the process owner measures the normal path, then a timeout, a stock discrepancy and the removal of channel access. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. Here the risk is concrete: a sudden migration can sacrifice revenue, while delay perpetuates risk. That is why the measure cannot be only the number of orders. We add margin, recovery time and the percentage of cases resolved without manual export.

10. Control lens: the decision for the 90-day independence plan

When we analyze the 90-day independence plan, the question about control shows whether the advantage remains with the merchant after the session and campaign have ended. In the architecture register, the source, adapter, destination and the available alternative are compared if the intermediary does not respond. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. The commercial consequence of the scenario is that a sudden migration can sacrifice revenue, while delay perpetuates risk. The verifiable answer remains: reduce dependence in stages, keeping profitable channels as adapters. The acceptance threshold is written before the test, not after the results are known.

11. Reconciliation lens: the decision for the 90-day independence plan

In the case of the 90-day independence plan, the lack of a definition for reconciliation shifts the discussion toward impressions and hides who bears the exception, loss or rule change. The pilot documents separately the effect on conversion, operating cost and the ability to resume the direct relationship. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. If we observe that a sudden migration can sacrifice revenue, while delay perpetuates risk, the pilot returns to the direct path. The team must reduce dependence in stages, keeping profitable channels as adapters, then repeat the test with the same products, markets and rules.

12. Margin lens: the decision for the 90-day independence plan

Seen through the margin lens, the 90-day independence plan is no longer an isolated function, but a decision about how value moves between store, customer and intermediary. The technical contract tests mandatory fields, intermediate states and the proof used when two systems disagree. The owner, verification frequency, minimum data and what cannot be inferred from the dashboard are noted. A favorable result on one day does not replace cohort testing, and a single incident does not justify removing the channel. This angle does not prove that the intermediary is useless; it proves that a sudden migration can sacrifice revenue, while delay perpetuates risk. For balance, the recommendation is to reduce dependence in stages, keeping profitable channels as adapters and to keep the channel only as long as it remains incremental.

Security and access minimization

The adapter does not receive general access just because it is called an "agent". Each operation has a purpose, identity, permissions, expiry and log. Tokens are limited to the resource and duration required, and secrets do not go into feeds, prompts or logs. For the 90-day independence plan, the threat model includes agent spoofing, replay, price manipulation, stock enumeration, promo abuse and data exfiltration. Sensitive actions require confirmation or explicit policies. Anti-bot protection is not disabled globally; legitimate traffic is authenticated and rate-limited on controlled commercial routes.

The alternative: direct commercial infrastructure

Independence does not mean blocking Google, marketplaces or agents. It means the core works without them: own catalog and stock, own price engine and checkout, CRM and consent, first-party analytics, plus a conversational channel on the website or WhatsApp. UCP, ACP or other protocols become adapters. For the 90-day independence plan, the design rule is that removing the adapter must not erase the product, the customer, the order history or the support capability. In this way, distribution can be changed without migrating the entire business.

What we measure

The minimum dashboard separates distribution from business health. For distribution: impressions, eligible appearances, sessions and orders by channel. For economics: net revenue, margin after discounts and operating cost, cancellations, returns and support. For relationship: identified customers, valid consents, direct returns and cohort value. For resilience: the percentage of portable catalog, reconciled orders, detection time and time to replace the adapter. In the theme of the 90-day independence plan, a single conversion rate cannot cover all these effects.

Frequently asked questions

What does the 90-day independence plan concretely change?

It changes where some commercial decisions are made or executed; it does not automatically move all responsibilities and does not guarantee distribution.

What is the main risk in this case?

A sudden migration can sacrifice revenue, while delay perpetuates risk. The risk is verified in contracts, data and flows, not assumed from the product name.

Does an open standard eliminate dependence?

Not automatically. The specification may be open, while eligibility and the interface remain controlled by a distributor.

Can we prepare the store before eligibility?

Yes: own catalog, deterministic offer, checkout, idempotency and adapters. Preparation should not be presented as live access.

What decision does the analysis recommend?

To reduce dependence in stages, keeping profitable channels as adapters, with success and stop thresholds written before the pilot.

Should Google be abandoned?

No. Google can remain a profitable channel; the goal is for it not to become the only commercial infrastructure.

Conclusion

A 90-day plan for detaching ecommerce from Google without losing sales is not an invitation to isolation. It is an invitation to the correct accounting of control. If a sudden migration can sacrifice revenue, while delay perpetuates risk, the short-term advantage must be compared with portability, the direct relationship and the exit cost. The healthy decision is to reduce dependence in stages, keeping profitable channels as adapters. Note the assumptions before the pilot, set stop thresholds and repeat the evaluation when countries, interfaces or contracts change. A good integration must be explainable both to the technical team and to sales, support and management. For an audit of visibility and dependencies you can talk with AYSA; for catalog, checkout, CRM and adapters you can see software development or start a direct discussion.

Sources and verification date

Sources verified on 24 August 2026. Eligibility, countries and commercial features may change; verification must be repeated before implementation. The analysis separates public documentation from editorial recommendations.