Price the deployment you need

Define the jobs you want DiscoveryOS to perform, then agree the modules, usage and implementation scope. A useful quote should make the charging basis, assumptions and responsibilities clear enough for commercial and technical teams to evaluate together.

## Start with the required scope List the storefronts, markets and shopper journeys in the proposed deployment. Identify the search, recommendation, retail-media or pricing workflows involved and the systems that will continue to own adjacent responsibilities.

## Prepare the usage assumptions Bring catalogue size, expected request volumes, seasonal peaks and the environments you need. Distinguish measured current usage from a forecast. Ask which events count towards the proposed charging unit and how retries, test traffic and overages are handled.

## Include implementation and operation Record the work needed for catalogue mapping, events, presentation, testing and launch. Identify who maintains each integration and which support arrangements are included. Keep one-off implementation costs separate from recurring charges.

## Request a quote you can compare Ask for the currency, billing period, included scope, usage assumptions, additional charges and renewal conditions in writing. Evaluate alternatives using the same operating period and requirements. Do not calculate savings by comparing one vendor’s full deployment with another vendor’s entry-level component.

## Plan the first evaluation Agree the scope of a demonstration or evaluation before treating it as a production commitment. Record the test data, acceptance criteria and decision owner, then connect the result to the proposed implementation and commercial terms.

Frequently asked questions

Is there a single price that applies to every deployment?

A useful commercial comparison needs the proposed modules, usage and implementation scope. Request a written quote with its charging basis and assumptions rather than treating an illustrative evaluation price or another customer’s contract as a universal production price.

How long will integration take?

The schedule depends on data readiness, storefront changes, event validation and the teams available to complete them. Build the timeline from agreed dependencies and acceptance criteria instead of using a generic launch promise.

Does the public MCP provide access to my store?

No. The public discovery surface describes PA’s public information and planning tools. Access to a retailer’s production data or operational systems requires a separate integration with the appropriate permissions and contract.