PIES Product Data Management

ACES gets your part
through the door.
PIES sells it.

ACES answers one question: does this part fit this vehicle? PIES answers everything else. It is the product's full commercial story — descriptions, attributes, pricing, digital assets, marketing copy, interchange, kitting. Most brands treat PIES as the paperwork that gets them listed. The brands who treat it as a commerce engine are the ones winning the shelf.

The Compliance Trap

The minimum gets you listed. It does not get you sold.

Auto Care's minimum for a PIES Item record is three fields: Part Number, Brand ID, and Part Type ID. It is worth noting that by the time a brand has submitted an ACES file, a trading partner already knows the brand — declared either at the ACES header level or at the individual application level, one or the other — and already knows every part number and part type from the application records. A PIES file built only to those three minimum fields adds no commercial information a trading partner didn't already have.

Most major trading partners have their own content requirements that extend well beyond Auto Care's floor. But even meeting those requirements does not mean a brand has built anything commercially meaningful. Many brands submit a description or two — often the same copy pasted across every part number in a category. No pricing data. No digital assets. Minimal attributes. A generic marketing line that says nothing about why this part, for this vehicle, is the right choice.

This is not a laziness problem. It is a tool problem compounded by an expertise problem. Spreadsheets cannot manage PIES content at scale. They cannot validate against the PAdb. They cannot flag duplicated descriptions, missing attributes, or assets that reference files that don't exist. And without expert guidance, most brands have no way to know what good looks like — or what it costs them commercially to never get there.

That gap is not a content problem. It is a platform problem. Auto Plus is built to close it.

Auto Care Minimum — Already in ACES
Part Number — declared in ACES
Brand ID — declared in ACES
Part Type ID — declared in ACES
A PIES file containing only these three fields tells a trading partner nothing commercially useful they didn't already know from the ACES submission. Compliance without commerce content is an empty file.
DescriptionsMany brands: 1–2, often copy-pasted across SKUs. Multiple codes available for different commercial purposes.
Partial
PricingMany brands submit no pricing data whatsoever.
Often missing
EXPITrade compliance, sourcing, warranty data. Widely ignored by most brands.
Often missing
AttributesTechnical specs. Frequently incomplete or misapplied.
Partial
Digital AssetsImages, documents, video. Quality and completeness vary widely.
Partial
PackagePackaging dimensions, quantity, Hazmat, EPR. Frequently overlooked.
Often missing
InterchangeCross-reference data. Largely ignored by most brands.
Rare
KittingBundle and kit relationships. Almost universally absent.
Rare
The gap between minimum compliance and full commercial depth is where parity lives — and where the opportunity is.
PIES Architecture

Built for commerce. Used for compliance.

Three parent segments. The Item segment carries eight child segments — none required, all purposeful. Auto Plus users maintain their own Auto Care standard subscriptions. Rivers Edge maintains active subscriptions independently for development and validation purposes, and is current on the PIES 8.0 standard.

Parent Segment
Marketing Copy
Brand-level marketing content and messaging
Parent Segment
Price Sheet
Structured pricing framework and terms
Parent Segment
Item
The product record — with 8 child segments
Description
Multiple description codes, each serving a specific commercial purpose. Some codes loop — allowing multiple entries to build layered supporting content around a primary narrative. Others are single-use and should carry a curated, substantive marketing statement. Most brands use one or two codes with duplicated copy across SKUs. The standard supports far more depth than most brands ever build.
Price
Line-item pricing tied to Price Sheet structures. Without structured pricing in PIES, trading partners determine the pricing context. The brand cedes control of one of its most commercially sensitive data points.
EXPI
Extended product information covering country of origin, core class and group, NAFTA/USMCA compliance, HTS classification, warranty terms, and more. Trade compliance and sourcing data essential for accurate distribution across the supply chain.
Attributes
Technical specifications validated against the PAdb standard. The only PIES segment — parent or child — that permits custom field names, which has created a misuse pattern of brands forcing content into Attributes that belongs elsewhere. When the PAdb is used correctly, the Part Type ID declared at the Item level determines which PAdb attribute IDs are valid for that part type. Of those valid attributes, some carry defined valid values that must be correctly selected. Most solution providers cannot tell a brand which PAdb IDs apply to their declared part type. Fewer still can guide them to the correct valid value within those. Auto Plus handles all three levels.
Requires expertise to implement correctly.
Package
The only Item child segment with its own child segments: Hazmat and the newly introduced EPR (Extended Producer Responsibility) in PIES 8.0. Packaging dimensions and quantity per package for warehousing, freight, and fulfillment accuracy.
Interchange
Cross-reference data connecting your part to OEM numbers, competitor SKUs, and legacy equivalents. A consumer searching for a Toyota filter part number they pulled from their engine bay should find your brand alongside every equivalent in the market — Wix, K&N, ACDelco, Motorcraft, and more.
Kitting
Component relationships for kits and bundles. Defines what ships together, what installs together, and what a buyer needs to complete the job — structured as data, not buried in a description field.
Digital Assets
Images, installation guides, specification documents, and video references structured and delivered with the product record. In ecommerce, the asset library replaces the physical experience of evaluating a part. Incomplete assets are lost sales.
None of the child segments are required by the standard. All of them exist because PIES was built for commerce, not just data exchange. Every segment a competitor skips is shelf space they have left uncontested. Rivers Edge is current on PIES 8.0, which introduces new capabilities including the EPR child segment under Package.
The Full Picture

PIES was built for commerce. Hardly anyone uses it that way.

The standard was not designed to create a list of parts. It was designed to communicate the complete commercial reality of a product — what it is, what it does, what it costs, what it replaces, what ships with it, and what a buyer needs to make a confident decision.

In ecommerce, PIES is the product experience. There is no showroom. No salesperson. No box to open before purchase. The data is the product until it arrives. Descriptions that actually describe — curated, not copy-pasted. Attributes that answer technical questions before they are asked. Interchange data that captures the buyer who searched for a competitor's part number.

In agentic commerce — where AI systems query, evaluate, and recommend products on behalf of buyers — richly structured PIES data is not a nice-to-have. It is the difference between being found and being invisible. An AI agent cannot recommend what it cannot read. And it cannot read a PIES file with two copied descriptions and no attributes.

"The brands that win on the digital shelf stopped treating PIES as a destination and started treating it as a starting point."

Descriptions Built for Commerce

Multiple description codes, each serving a specific commercial purpose. Some loop — building layered supporting content around a primary narrative. The primary marketing description is single-use and deserves careful, substantive curation. Generic copy pasted to every SKU is noise that serves nobody. The difference between the two is expertise and a platform that makes quality manageable at scale.

Attributes That Require Precision

The Part Type ID declared at the Item level determines which PAdb attribute IDs are valid to use. Of those, some carry defined valid values that must be correctly selected. Most solution providers cannot navigate even the first step — identifying which PAdb IDs apply to a given part type. Fewer still can guide brands to the correct valid values within those. When attributes are built to this depth, they power search, filtering, and compatibility matching at scale. When they are not, they are noise the trading partner cannot use.

Interchange That Captures Market Share

A buyer with a dirty OEM filter in their hand is not searching for your brand name. They are searching for the part number they can read. Properly managed interchange puts your product in that result — alongside every equivalent in the market.

Pricing on Your Terms

Structured price sheets with line-item pricing tied to your PIES Item records. Without this, trading partners fill the gap on their terms. Pricing is a commercial signal. Brands who manage it in PIES control that signal. Those who don't have surrendered it.

Digital Assets That Replace the Shelf

Images, installation documents, specification sheets, video references — structured and delivered with the product record. A buyer evaluating your part online needs to see what they cannot hold. Incomplete assets are not a minor gap. They are a conversion killer.

Beyond the Standard

PIES is the floor. Auto Plus takes you above it.

Full PIES compliance is the starting point. As PIES product data management software, Auto Plus includes proprietary capabilities that take brands well beyond what the standard requires — into the territory where parity breaks and competitive differentiation begins.

Content Enrichment

Build above the standard — systematically.

Auto Plus includes tools for enriching PIES content across every segment at scale. Not part by part, one field at a time — systematically, across a full catalog, with the consistency that trading partners and AI systems require to work with your data effectively.

Upsell & Alternate

Every sale is a second opportunity.

Structured upsell and alternate part relationships built into the product record — the upgrade that increases order value, the alternative that keeps a sale in-house when the primary is unavailable. Commerce intelligence that lives in the catalog, not in a sales rep's head.

Validation & Accuracy

What leaves your system is what the standard will accept.

Every PIES segment validated against the current PAdb, PCdb, and PIES schema before export. Errors surfaced at the record level — not discovered after a trading partner rejects the file. Standards compliance that is verified, not assumed.

Agentic Commerce Readiness

Structured for what is already coming.

Complete descriptions, validated attributes, structured relationships, properly referenced digital assets — this is the data foundation AI systems need to find, evaluate, and recommend products. The brands building it now will own the advantage when it fully arrives.

PIES Standards & Databases
PIES Subscriber PAdb Subscriber PCdb Subscriber Brand ID Subscriber ACES Subscriber VCdb Subscriber Qdb Subscriber ECdb Subscriber PIES 8.0 Current
See It In Action

See what your PIES data could be doing for you.

Schedule a demo and bring your current PIES data. We will show you where the gaps are, what the full picture looks like, and what it takes to get there.

Standards Practitioner Since 2001