Order and checkout objects

This is the largest domain in the schema, because it holds both sides of a purchase: the cart while a shopper is still deciding, and the order once they have paid. Use this article to find the object you need before you query or report on sales data.

A cart becomes an order

The single most useful thing to know is that cart and order are parallel structures, not one record changing state.

A Cart holds Cart Items. At checkout StoreConnect creates an Order with Order Items, and the cart is kept rather than deleted. So a completed purchase exists twice, and which one you query depends on the question:

• What is in progress, or was abandoned? Query the cart.
• What was sold? Query the order. Prices on an order item are what was actually charged, not what the price book says now.

Fulfillment is decided on the cart, before the order exists. A Cart Fulfillment is one delivery method for part of the basket, and Cart Fulfillment Item assigns items to it. That is how one order ships some items and holds others for pickup.

Money is separate from the order

A Payment is one attempt to move money, so an order can have several: a failed attempt, a retry, a partial refund. The order’s paid state is the sum of its payments rather than a field someone sets.

Payment Item is the record that allocates part of a payment to a particular order or fulfillment, which matters when one payment covers a split shipment, or one order is paid by card and voucher together.

:::note A Payment Provider is the configured gateway. A Payment Method is what the shopper sees at checkout. One provider usually offers several methods, and surcharges are set on the method. :::

Two generations of promotions

The schema carries both promotions models, which is the most common source of confusion here.

Promotion (s_c__Promotion2__c) is the current model. Its conditions say what a cart must satisfy, its product scope limits what it applies to, and usage records enforce limits.

The objects labeled Legacy Promotion in the table below are the superseded model, kept so existing data still reads. Write against the current model.

Discount is a different thing again: it reduces a price automatically, with no code entered.

Objects in this domain

Where it meets other domains

• Catalog. Cart items, order items, and promotion scopes all point at products and categories. Prices come from the price book, not the product. See catalog objects.
• Customers and accounts. An order belongs to an account and a contact, and account credit is spent through payments. See customer and account objects.
• Fulfillment and inventory. Cart fulfillments become shipments and fulfillment items after checkout, and stock moves when they do. See fulfillment and inventory objects.
• Point of sale. A POS sale creates the same cart, order, and payment records as the web, linked to the register and shift that took it. See POS objects.

Tax and promotion scoping both run through join records. If you are querying or importing one, junction objects explains what that means.