building-b2b

Configure Celigo B2B Manager EDI integrations with trading partner templates and envelopes.

3|2|Updated May 20, 2026
One-click install
npx skills add https://github.com/celigo/ai --skill building-b2b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-b2b
Source: https://github.com/celigo/ai/tree/main/skills/building-b2b
Command: npx skills add https://github.com/celigo/ai --skill building-b2b

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design and implement Celigo B2B Manager EDI (X12/EDIFACT) integrations without getting stuck on the many required components and configuration details.

Core Features & Use Cases

  • Trading partner onboarding: Start from or align to a trading partner connector template for connection, EDI profile defaults, and export/import requirements.
  • Correct EDI envelope + parsing/generation: Configure the EDI profile (ISA/GS for X12, UNB for EDIFACT) and create partner-specific file definitions with the right delimiters and rules.
  • Operational visibility: Monitor processed EDI documents via transaction monitoring and acknowledgement (e.g., 997/CONTRL) status to troubleshoot exchange issues.

Use cases include onboarding new trading partners, editing existing X12/EDIFACT flows, setting parsing rules for specific document types (e.g., 850/856, ORDERS/INVOIC), and validating that documents are being received and acknowledged correctly.

Quick Start

Ask your AI agent to guide you through creating a trading partner connector, then setting up an EDI profile, file definitions, and the inbound/outbound export-import pair for a Costco-style 850 workflow.

Frequently Asked Questions about building-b2b

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up EDI B2B integrations for new trading partners?

EDI file definitions require configuring the correct standard delimiters, parsing rules, and immutable fields such as fileType and globalId. You must accurately link the export and import resources to the referenced EDI profile and file definition identifiers to ensure documents like 850 or 856 are parsed and generated correctly.

How do I monitor EDI transactions and acknowledgement status?

Monitoring processed EDI transactions involves checking transaction monitoring tools and acknowledgement status, such as X12 997 or EDIFACT CONTRL. This operational visibility helps you verify that documents are received correctly and troubleshoot any exchange issues with your trading partners.

Does this approach support both X12 and EDIFACT EDI standards?

Yes, the approach supports both X12 and EDIFACT EDI standards. You can configure the respective EDI profiles, interchange envelopes, and partner-specific file definitions to handle various document types like 850, 856, ORDERS, or INVOIC across different trading partner workflows.

What is needed to correctly configure an EDI profile for X12 or EDIFACT?

Configuring an EDI profile requires setting up interchange envelopes, specifically ISA and GS segments for X12 or UNB for EDIFACT. You must ensure valid standard delimiters and rules are applied, and that partner-specific file definitions are accurately linked to the profile for successful document exchange.

Why are my EDI export and import resources not linking correctly?

EDI export and import resources fail to link correctly when the referenced EDI profile and file definition identifiers are inaccurate. Ensure that immutable fields like fileType and globalId are correct, and that valid standard delimiters and rules are applied to the document-specific file definitions.