Database Reference

PunchOut connects procurement identities and shopping sessions with standard Magento customers, quotes and orders. The relationships below focus on the records an implementation or ERP team is likely to encounter.

Buyers and mappings

Relationship	Why it matters
`punchout_buyer_config` belongs to one `store`	Selects the Store View used for the buyer's PunchOut sessions.
`punchout_buyer_config` can use one `customer_entity`	Supports a fixed Magento customer for a procurement identity.
`punchout_buyer_config` can use one `customer_group`	Provides the customer group used when just-in-time provisioning is enabled.
`punchout_buyer_config` can use one `punchout_mapping_profile`	Selects the outbound field mapping for the buyer and protocol.
`punchout_mapping_rule` belongs to one `punchout_mapping_profile`	Defines how Magento values are written into OCI or cXML fields.
`punchout_mapping_value_map` belongs to one `punchout_mapping_rule`	Translates known source values for a specific mapping rule.

Session and returned cart

Relationship	Why it matters
`punchout_session_context` belongs to one `store`	Keeps protocol handling within the Store View selected for the session.
`punchout_session_context` can identify one `customer_entity`	Connects the procurement user to the resolved Magento customer.
`punchout_session_context` can use one `quote`	Links the active PunchOut context to its Magento shopping cart.
`punchout_returned_cart_snapshot` can belong to one `punchout_buyer_config`	Records which buyer received the returned cart.
`punchout_returned_cart_snapshot` can refer to one `quote`	Preserves the original cart context used for later order comparison.

Inbound orders and document loop

Relationship	Why it matters
`punchout_inbound_order` can belong to one `punchout_buyer_config`	Applies the correct buyer policies to an incoming order document.
`punchout_inbound_order` can identify one `customer_entity`	Records the Magento customer resolved for the order.
`punchout_inbound_order` can refer to Magento `quote` and `sales_order`	Connects the procurement document to the cart and order it created or updated.
`punchout_inbound_order` can refer to original and replacement `sales_order`	Preserves order history when the configured update policy creates a replacement.
`punchout_confirmation_line` belongs to one `punchout_inbound_order`	Stores line-level confirmation results for the procurement response.
`punchout_document_queue` can belong to one `punchout_session_context` or `punchout_inbound_order`	Keeps confirmations, ship notices and invoices tied to their business transaction.

Operations and add-on data

Relationship	Why it matters
`punchout_trace` can belong to one `punchout_session_context`	Groups diagnostic stages for the same PunchOut exchange.
PunchOut analytics records belong to one `store`	Keeps usage and item analytics Store View specific.
`punchout_iframe_buyer_config` belongs to one `punchout_buyer_config`	Adds embedded-session policy to an existing buyer without duplicating its credentials or protocol settings.

Payload contents, credentials, replay data and internal queue fields are intentionally omitted. Use the PunchOut services and Admin screens so authentication, idempotency and order policies remain enforced.