Common Workflows

Connected Data, Read to Use

A few examples of how dPivot connects the systems, products, files, and APIs that sit between an organization and the customers.

01 / Product Content and Imagery

Turn an ERP export into product-ready content.

Parts arrive from an ERP or another external system. dPivot ingests and normalizes the export, prepares the products for API consumption, and maps incoming images to the products they belong to.

Assets are optimized for web and mobile, then exposed through a product API.

Unlike a traditional DAM, products linked to one or more images ensure that every image stays in product context—ready.

How it flows

ERP exportNormalizeMap imagesProduct API

Dealers , Brochures, Web sites, Partners

02 / Parts-to-Vehicle Fitment

Help every visitor find the right part for their vehicle.

Vehicle and product data comes from Salesforce, an ERP, or other source systems. dPivot ingests and normalizes it, then connects products to vehicles and engines through a parts-to-vehicle fitment engine.

The fitment API turns source data into a product-finding experience that an ERP alone does not provide.

How it flows

Source systemsNormalizeMatch fitmentFitment API

Vehicle selector, Product pages, Dealer and internal company tools

03 / Product Documents

Put the right manual or sales sheet beside every product.

Product manuals, sales sheets, marketing materials, and spare parts catalogs are ingested from an ERP or file source. dPivot normalizes the files and joins each document to the products it describes.

A consumable API exposes the documents to a website, dealer portal, or other customer-facing system.

Instead of a disconnected ERP file list, each product can expose only the documents that matter to the customer.

How it flows

ERP filesNormalizeJoin to productsDocument API

Manuals , Sales sheets , Parts catalogs