Manufacturing integration

Campari Group EDI integration

How EDI and API integration with Campari Group typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Campari Group.

At a glance

Campari Group integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Campari Group program or a customer relationship.

Illustration of a factory with a conveyor carrying boxes, representing the manufacturing industry that Campari Group operates in.
Industry. Manufacturing: where Campari Group operates.
Workflow diagram: your ERP and warehouse systems exchange documents with Campari Group through ECOM. You send 850, 867, 852, 820; you receive 855, 856, 810, 846; 997 acknowledgments go both ways. Your systems ERP · warehouse · finance ECOM integration map · validate · connect · monitor Campari Group 850 867 852 820 850 867 852 820 855 856 810 846 855 856 810 846 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Campari Group

Tell us which documents you exchange with Campari Group, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Campari Group.

  • Review of Campari Group's requirements with you, once you have them
  • EDI and API integration with your ERP and warehouse systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Campari Group

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Campari Group integration fits your systems

Your systemsERP, WMS and accounting
ECOMMapping, validation, connectivity and monitoringAS2 or SFTP · EDI network (VAN) · API or web portal
Campari GroupIts program, documents and requirements
  1. ConfirmConfirm your Campari Group program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding Campari Group integration

Who this is for: Distributors, retailers and other customers that buy from Campari Group, and the order, shipping and finance teams that support them.

Scope: This guide describes typical practice for this kind of trading relationship; Campari Group's own program details are confirmed during onboarding.

Campari Group is an Italian spirits company whose brands include Campari, Aperol, Wild Turkey and Espolòn. Wine and spirits are sold through licensed distributors and state-regulated channels, so order and shipment data is paired with price postings, allocations and depletion reporting.

US sales combine imported Italian aperitifs and American whiskey, so import documents, state distributor orders and allocation controls apply across product lines. In this kind of program the points that usually matter are state price postings, allocated products, distributor depletions and lot or vintage data. Campari Group's own EDI or API specification is not part of this guide and no Campari Group document was read, so treat the document list and workflows below as typical practice for this type of company and confirm the documents, X12 version, delivery method and testing steps with Campari Group before you build.

ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications, and then monitors every file after go-live and handles partner changes, as software, as a managed service or both.

Business scenarios

Where Campari Group integration gets complicated

Typical requirements—confirm with your trading partner.

Working with Campari Group

US sales combine imported Italian aperitifs and American whiskey, so import documents, state distributor orders and allocation controls apply across product lines.

How ECOM helps: ECOM connects orders, acknowledgments, ship notices and invoices to your ERP and warehouse systems, and lists differences between ordered, confirmed and shipped quantities.

What you gain: Fewer allocation disputes and faster invoice matching.

Depletion and resale reporting

Producers expect wholesalers to report what moved to retail, so they can plan production and reconcile promotions, and the layout can differ by state and by producer. Confirm the layout Campari Group asks for.

How ECOM helps: ECOM maps your resale data into the product transfer and resale (867) and product activity (852) layouts the producer asks for, and checks totals against what you received before the file is sent.

What you gain: Fewer credit and promotion disputes caused by reports that do not match shipments.

Ordering across product lines

Orders to Campari Group can span several product lines, pack sizes and allocated or seasonal items that ship on different dates and have to be received together.

How ECOM helps: ECOM tracks each order, acknowledgment and ship notice against your plan and shows what is late, short or substituted.

What you gain: Fewer stock-outs caused by items that arrive late or short.

Workflows

Typical Campari Group business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not Campari Group's published process.

Distributor orders

  1. 1Send 850 order
  2. 2Receive 855 confirmation
  3. 3Receive 856 ship notice
  4. 4Receive 810 invoice

Depletion reporting

  1. 1Collect sales by item
  2. 2Send 867 or 852
  3. 3Reconcile with shipments
  4. 4Resolve differences

Documents and APIs

Campari Group documents by program

General guidance. We could not verify Campari Group's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Campari Group's confirmed requirements. Confirm the list, versions and programs with Campari Group.

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order To Campari Group If you buy from Campari Group General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment From Campari Group If you buy from Campari Group General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest From Campari Group If you buy from Campari Group General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice From Campari Group If you buy from Campari Group General guidance Typically bills for what shipped, matched against the order.
867 Product Transfer and Resale Report To Campari Group If you buy from Campari Group General guidance Typically reports product sold or transferred, so the maker can reconcile pricing, credits and depletions.
852 Product Activity Data To Campari Group If you buy from Campari Group General guidance Typically reports sales or stock movement by item and location, where a program uses it.
846 Inventory Inquiry/Advice From Campari Group If you buy from Campari Group General guidance Typically shares inventory positions or availability between the two sides.
820 Payment Order/Remittance Advice To Campari Group If you buy from Campari Group General guidance Typically explains what a payment covers, so cash can be applied to the right invoices and deductions.
997 Functional Acknowledgment Both directions If you buy from Campari Group General guidance Typically confirms that each file was received and could be read.
850 Purchase Order From Campari Group If you supply Campari Group General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment To Campari Group If you supply Campari Group General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest To Campari Group If you supply Campari Group General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice To Campari Group If you supply Campari Group General guidance Typically bills for what shipped, matched against the order.
997 Functional Acknowledgment Both directions If you supply Campari Group General guidance Typically confirms that each file was received and could be read.

Connectivity

How companies connect

  • AS2 or SFTP

    Many companies exchange EDI files directly over AS2 or SFTP.

    General guidance

  • EDI network (VAN)

    Many suppliers connect through a value-added network that delivers files to and from the partner and keeps an audit trail.

    General guidance

  • API or web portal

    Some programs use REST or SOAP APIs, a supplier portal or a cloud EDI service for some documents. A login is usually required for portals.

    General guidance

Challenges

Common integration challenges

  • Price postings and state rules

    Pricing and shipment rules differ by state. Details depend on your distributor agreement.

  • Allocated product

    Limited releases need quantity control from order to invoice.

  • Depletion layouts

    Each distributor may report sales in its own format and schedule.

  • Lot and vintage data

    Where lot or vintage is tracked, it has to carry through shipment documents.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set by Campari Group. ECOM works from them during mapping and testing.

Automation options for Campari Group customers

Four ways to automate. One foundation.

ECOM helps you automate the orders you send and the acknowledgments, ship notices and invoices you receive, connect them to your systems, and see what needs action. Campari Group sets its own requirements; ECOM reviews them with you and confirms which options fit.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect Campari Group documents to your ERP

ECOM connects the documents you exchange with Campari Group to your ERP and warehouse systems, so orders post without re-keying and ship notices and invoices come from the data you already hold.

Industry

Food and Beverage

See how ECOM supports EDI for food and beverage suppliers and buyers.

Solution

Order-to-Cash Automation

Connect orders, shipments, invoices and payments into one order-to-cash flow.

Service

Fully Managed EDI

Have ECOM run your EDI connections, monitoring and partner changes.

Zero Trust for EDI and file transfer

Zero Trust EDI and MFT for your Campari Group connection

Exchanges with Campari Group move business documents between your systems and an outside party. A Zero Trust design assumes no connection, file or user is safe by default.

  • Authentication

    Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.

    Business outcome: A lost or reused credential affects one partner, not all of them.

  • Least privilege

    Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.

    Business outcome: A mistake or compromise in one account stays limited to what that account could reach.

  • Isolation

    Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.

    Business outcome: Outside connections do not land directly on your internal systems.

  • Encryption

    Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.

    Business outcome: Less exposure if a file is intercepted or a file store is reached.

  • Certificate and key management

    Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.

    Business outcome: Fewer outages caused by an expired certificate or key.

  • Monitoring and access controls

    Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.

    Business outcome: Late, missing or failed files are noticed early, before they hold up payment, shipping or reporting.

  • Audit trail

    Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.

    Business outcome: You can answer who sent what and when, for your own audits and partner reviews.

What this means for your data

Partner access

Each trading partner connects with its own identity and a limited scope, and any connection can be reviewed or removed on its own.

File and document handling

Documents are verified when they arrive and every transfer is logged.

Exceptions

Late, missing or rejected files raise an alert and go to a named owner.

Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. Campari Group may set its own security requirements, which come first.

General EDI flow

How EDI with Campari Group typically works

The documents, their order and the timing are Campari Group's to set; this is the general sequence most programs of this kind follow.

  1. 850 Purchase Order

    From you to Campari Group

    Typically carries the order: items, quantities, prices, ship-to locations and requested dates.

  2. 855 Purchase Order Acknowledgment

    From Campari Group to you

    Typically confirms an order, or reports changes to quantities, prices or dates.

  3. 856 Ship Notice/Manifest

    From Campari Group to you

    Typically tells the receiver what is on each shipment, often with carton or pallet label details.

  4. 810 Invoice

    From Campari Group to you

    Typically bills for what shipped, matched against the order.

  5. 867 Product Transfer and Resale Report

    From you to Campari Group

    Typically reports product sold or transferred, so the maker can reconcile pricing, credits and depletions.

  6. 852 Product Activity Data

    From you to Campari Group

    Typically reports sales or stock movement by item and location, where a program uses it.

  7. 846 Inventory Inquiry/Advice

    From Campari Group to you

    Typically shares inventory positions or availability between the two sides.

  8. 820 Payment Order/Remittance Advice

    From you to Campari Group

    Typically explains what a payment covers, so cash can be applied to the right invoices and deductions.

  9. 997 Functional Acknowledgment

    Both directions

    Typically confirms that each file was received and could be read.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your Campari Group program

Each request goes to an ECOM EDI specialist with Campari Group's name attached, so the reply starts from your program.

  • Review Campari Group's requirements

    Send us Campari Group's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Campari Group to your ERP

    Purchase orders out, acknowledgments, ship notices and invoices in, connected to the ERP and receiving systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Campari Group document, then go live with monitoring from the first file.

    Plan testing and certification

Campari Group integration FAQs

Does Campari Group use EDI?

Companies of this type commonly exchange EDI or APIs with suppliers and customers. This page does not include Campari Group's requirements.

Are you supplying Campari Group or buying from it?

The documents differ. Suppliers usually receive orders or schedules and send ship notices and invoices; buyers usually send orders and receive acknowledgments, ship notices and invoices. This page shows both views.

What is different about working with Campari Group?

US sales combine imported Italian aperitifs and American whiskey, so import documents, state distributor orders and allocation controls apply across product lines.

Which EDI documents are typical for this kind of company?

Typical documents are 850, 855, 856, 810, 867, 852, 846, 820, 997. That is general practice, not Campari Group's published list.

How does onboarding with Campari Group usually work?

Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on Campari Group's requirements, test cycles and your ERP.

Does this guide mean Campari Group endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by Campari Group.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. Campari Group sets its own requirements and can change them at any time; your Campari Group implementation guide, supplier portal or account contact is the authoritative source for your program.

  • Campari Group: company website Official Campari Group source
  • ASC X12: transaction set reference (standards body) Standards reference
  • Campari Group: company description Background, not checked against a company source The description of Campari Group comes from general public knowledge and was not checked against Campari Group's own website for this page.
  • Campari Group: no company document read Background, not checked against a company source No Campari Group supplier, customer or integration document was read for this page. Everything shown is typical practice for this type of company.

Request Campari Group integration assistance

Tell us about your Campari Group program, documents and ERP. We will outline the connection, mapping and testing plan.