--- title: "Shipping" description: "A non-technical overview of Shipping in RevCent, focused on shipment records as item-level commerce objects created from shippable products, how they connect to Fulfillment Accounts and Shipping Profiles, how tracking and delivery updates work, and how shipping supports support, automation, chargeback evidence, and BigQuery reporting." type: "item" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/item/Shipping.md" relationships: - name: "Fulfillment Account" url: "https://revcent.com/documentation/markdown/ecosystem/feature/FulfillmentAccount.md" - name: "Shipping Profile" url: "https://revcent.com/documentation/markdown/ecosystem/feature/ShippingProfile.md" technical_links: web_app: "https://kb.revcent.com/en/revenue/shipping" api: section: "https://revcent.com/docs/api/v2#section-shipping" operations: - name: "Get Shipments" operation_id: "GetShipments" operation: "https://revcent.com/docs/api/v2#operation-GetShipments" schema: "https://revcent.com/documentation/files/api/operation/GetShipments.json" - name: "Get A Shipment" operation_id: "GetShipment" operation: "https://revcent.com/docs/api/v2#operation-GetShipment" schema: "https://revcent.com/documentation/files/api/operation/GetShipment.json" - name: "Edit A Shipment" operation_id: "EditShipment" operation: "https://revcent.com/docs/api/v2#operation-EditShipment" schema: "https://revcent.com/documentation/files/api/operation/EditShipment.json" - name: "Refund A Shipment" operation_id: "RefundShipment" operation: "https://revcent.com/docs/api/v2#operation-RefundShipment" schema: "https://revcent.com/documentation/files/api/operation/RefundShipment.json" - name: "Search Shipping" operation_id: "SearchShipping" operation: "https://revcent.com/docs/api/v2#operation-SearchShipping" schema: "https://revcent.com/documentation/files/api/operation/SearchShipping.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewShipping.md" operations: - name: "Get Shipments" operation_id: "GetShipments" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetShipments.md" available_via_ai: true - name: "Get A Shipment" operation_id: "GetShipment" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetShipment.md" available_via_ai: true - name: "Edit A Shipment" operation_id: "EditShipment" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditShipment.md" available_via_ai: true - name: "Refund A Shipment" operation_id: "RefundShipment" markdown: "https://revcent.com/documentation/markdown/mcp/operation/RefundShipment.md" available_via_ai: true - name: "Search Shipping" operation_id: "SearchShipping" markdown: "https://revcent.com/documentation/markdown/mcp/operation/SearchShipping.md" available_via_ai: true bigquery_schema: "https://revcent.com/documentation/files/bigquery/dataset.json" bigquery_tables: - "shipping" --- # Shipping Shipping records are RevCent item records created when a shippable product needs to be shipped to a customer. A Shipping record is not the same as a Shipping Profile or a Fulfillment Account. A Shipping record is the individual shipment item created from commerce activity. A Shipping Profile is the configurable feature that helps determine shipping rates, providers, methods, and eligibility. A Fulfillment Account is the configurable feature that connects shippable products and shipment activity to the fulfillment provider or software responsible for shipping. The practical idea is: ```text Shipping Profile = reusable shipping-rate and rule configuration Fulfillment Account = reusable fulfillment provider connection Shipping = individual shipment item created from a sale, renewal, or trial event ``` Shipping matters because selling a physical product does not end when payment is accepted. The business still needs the product to be sent to fulfillment, shipped, tracked, communicated to the customer, and available for support, automation, and reporting. --- ## Why Shipping Is an Item Shipping is an item because each Shipping record represents a specific shipment that was created from actual commerce activity. A business does not create one generic Shipping configuration and reuse it forever. Instead, RevCent creates Shipping records when a sale lifecycle requires a physical shipment. Conceptually: ```text Shippable product is configured ↓ Customer purchase, renewal, or trial event occurs ↓ RevCent creates commerce records ↓ RevCent creates a Shipping record ↓ The Shipping record can be fulfilled, tracked, edited, updated, refunded, reported on, and used by support workflows ``` This makes Shipping different from Fulfillment Accounts and Shipping Profiles. Those are configurable features. Shipping records are the individual shipment items created from those configurations and from commerce events. --- ## Technical Links | Area | Link | |---|---| | Web App | `https://kb.revcent.com/en/revenue/shipping` | | API | `https://revcent.com/docs/api/v2#section-shipping` | | MCP / AI | `https://revcent.com/documentation/markdown/mcp/operation/OverviewShipping.md` | | BigQuery Schema | `https://revcent.com/documentation/files/bigquery/dataset.json` | | BigQuery Tables | `shipping` | --- ## Core Purpose The core purpose of a Shipping record is to represent a shipment that needs to move through fulfillment and delivery. Shipping records help answer questions such as: - What product or products need to be shipped? - Who is the customer? - Where should the shipment be sent? - Which sale, renewal, trial, or product sale created the shipment? - Which Fulfillment Account is responsible for fulfillment? - Was the Fulfillment Account notified? - Which provider and provider method are associated with the shipment? - Has the shipment shipped? - Has delivery been confirmed? - What is the tracking number or tracking URL? - Was the customer notified when the shipment shipped or was delivered? - What shipping amount, cost, refund, or margin is associated with the shipment? - Is this shipment useful for support, revenue analysis, or chargeback evidence? For physical-product ecommerce, Shipping records are one of the main bridges between RevCent revenue activity and fulfillment operations. --- ## How Shipping Records Are Created A Shipping record is created when RevCent has a commerce event involving shippable products and enough shipping/fulfillment context to create the shipment. Common sources include: | Source | How Shipping Fits | |---|---| | Initial sale | A customer buys a shippable product. | | Pending sale processing | A pending sale with shippable products is processed. | | Subscription renewal | A shippable subscription product renews and needs a refill shipment. | | Trial expiration | A trial expires and product settings require shipment at expiration. | | Trial creation | Some trial products may ship when the trial is created, depending on product settings. | | Shippable bundle sale | A bundle or bundled component may require shipment. | | Third-party shop order | A WooCommerce or other connected shop order can create shipment context for mapped shippable products. | High-level flow: ```text Product is marked shippable ↓ Product has shipping attributes and a Fulfillment Account ↓ Sale, renewal, trial event, or shop order occurs ↓ RevCent creates Sale / Product Sale context ↓ RevCent creates Shipping record ↓ RevCent can notify the configured Fulfillment Account ↓ Tracking and status updates can be stored on the Shipping record ``` A subscription renewal with a shippable product can also create a Shipping item. This is important for subscription ecommerce because recurring billing and recurring fulfillment both need to happen. --- ## Shipping and Shippable Products A product must be configured as shippable for RevCent to treat it as requiring shipment. Important product-level concepts include: | Product Concept | Why It Matters | |---|---| | `is_shippable` | Indicates that the product requires shipping. | | `shipping_attributes` | Holds shipping-related product details. | | `shipping_attributes.fulfillment_account` | Identifies the Fulfillment Account that should handle fulfillment for the shippable product. | | trial shipping setting | Controls whether trial products ship at trial creation, trial expiration, or both. | Before a physical product is sold live, the business should verify that the product is shippable, the shipping attributes are complete, and the correct Fulfillment Account is assigned. A shippable product without a valid Fulfillment Account may create fulfillment problems because RevCent may not know which provider connection should handle the shipment. --- ## Relationship to Fulfillment Accounts A Fulfillment Account is the configured provider connection used to handle fulfillment for shippable products. A Shipping record can reference the Fulfillment Account that should receive the fulfillment handoff. Conceptually: ```text Fulfillment Account = configured provider connection Shipping record = specific shipment using that provider connection ``` When a shippable product is sold, renewed, or trial-expired in a way that requires shipping, RevCent uses the product's configured Fulfillment Account to notify the fulfillment provider/account. This means the normal fulfillment-provider notification should be handled by RevCent's built-in Fulfillment Account flow. Functions or external systems should not be positioned as the primary way to notify the fulfillment provider for standard shippable-product orders. Use Functions or external systems only for supplemental workflows, such as: - sending shipment context to a CRM or ERP - notifying Slack or an internal operations channel - creating a support ticket - notifying a custom dashboard - sending shipment data to a secondary non-fulfillment system - handling custom exceptions that do not duplicate the normal fulfillment handoff Correct boundary: ```text Core fulfillment notification = RevCent Fulfillment Account handling Supplemental automation = Functions, AI Assistants, Email Templates, external systems ``` --- ## Fulfillment Notification Fields Shipping records can include fulfillment notification context. Important fields include: | Field | Meaning | |---|---| | `fulfillment_account` | The Fulfillment Account associated with the shipment. | | `fulfillment_account_notified` | Whether the Fulfillment Account was notified to ship the shipment. | | `fulfillment_account_notified_date` | When the Fulfillment Account was notified. | These fields are operationally important. A sale may be paid, but if fulfillment was not notified, the product may not ship. Support, operations, and AI workflows can use these fields to identify shipments that need attention. --- ## Relationship to Shipping Profiles A Shipping Profile is the configurable feature that defines shipping rates and rules. A Shipping record is the item created when those shipping rules and the commerce event result in an actual shipment. A Shipping Profile can contain one or more rates. Each rate can include provider, provider method, cost, customer rate, and qualification rules. Shipping Profile rates can qualify by: - product rules - product group rules - revenue rules - destination country restrictions When multiple rates match, RevCent can use the most profitable matching rate based on the difference between the customer rate and cost. The distinction is: ```text Shipping Profile = rules for determining whether and how shipping should apply Shipping record = the shipment created from the sale, renewal, or trial event ``` --- ## Shipping Profiles and WooCommerce Initial Sales Shipping Profiles are especially important for trial and subscription based shippable products. For WooCommerce initial sales, RevCent accepts the shipping calculated by WooCommerce at checkout rather than using RevCent Shipping Profiles to calculate shipping for that initial sale. That WooCommerce exception applies to the initial checkout sale only. Future trial expirations or subscription renewals with shippable products still need RevCent shipping configuration to create shipping entries correctly. Operationally: ```text WooCommerce initial sale = WooCommerce shipping calculation can be accepted Future RevCent trial expiration / subscription renewal = RevCent shipping profile logic matters ``` If RevCent cannot find an applicable rate within the relevant Shipping Profile logic for a trial expiration or subscription renewal, the Shipping item may not be created and the product may not ship. --- ## Shipping Rates and Matching Rules A Shipping Profile rate determines the amount charged to the customer and the provider/method context for the shipment. Important rate concepts include: | Rate Concept | Meaning | |---|---| | customer rate | Amount charged to the customer for shipping. | | cost | Estimated business cost to ship the item. | | provider | Carrier or shipping provider, such as USPS, UPS, FedEx, or another supported provider. | | provider method | Shipping method for the provider, such as Priority Mail or Ground. | | qualifiers | Rules that decide whether the rate applies. | All enabled rules within a rate must pass for that rate to be considered valid. A rate does not need every type of rule, but it should have at least one meaningful qualifier. Examples: ```text Rate uses only revenue rule: If purchase amount is greater than a threshold, use this rate. ``` ```text Rate uses product rule: If purchase contains a certain quantity of a product, use this rate. ``` ```text Rate uses product + revenue rules: If purchase contains a product and amount is greater than a threshold, use this rate. ``` --- ## Shipping Provider and Provider Method A Shipping record can store the provider and method used for the shipment. In RevCent, provider and provider method values help the business understand how the shipment should be carried or was carried. Provider examples include carriers or shipping services such as USPS, UPS, FedEx, DHL, and other supported providers. The provider method identifies the service level or method for that provider. These values are useful for: - fulfillment handoff - customer support - tracking context - shipping-cost review - operational reporting - customer notification emails - chargeback evidence --- ## Tracking Numbers, Tracking URLs, and Delivery Status A Shipping record can store tracking-related fields such as: | Field | Meaning | |---|---| | `provider_tracking` | Tracking number. | | provider tracking URL | Tracking URL when available through the shipment/provider context. | | `shipping_status` | Overall shipping status. | | `ship_date` | When the shipment was shipped. | | `delivered_date` | When delivery was confirmed. | A tracking number or tracking URL does not automatically mean the shipment was delivered. Important distinction: ```text Tracking number available ≠ delivery confirmed ``` The Knowledge Base describes third-party shipment tracking for delivered-status updates. Once a shipment is marked shipped with a tracking number, delivery updates can be received through a supported third-party tracking integration if the business wants delivery status inside RevCent. Supported third-party delivery tracking services described in the Shipping documentation include: - EasyPost - Shippo These services are used for delivery-status updates. They are not required just because a business has a Fulfillment Account, and they should not be confused with the normal fulfillment handoff. --- ## When EasyPost or Shippo Is Needed EasyPost or Shippo is useful when the business wants delivery-level visibility in RevCent. Examples: - Know when a package was delivered. - Send delivery confirmation emails. - Trigger post-delivery follow-up workflows. - Support product-not-received investigations. - Build chargeback evidence around shipped or delivered products. - Let support or AI workflows answer delivery-status questions. - Analyze delivery timing and fulfillment performance. EasyPost or Shippo may not be necessary if the business only needs: - tracking numbers - tracking URLs - basic shipped status - manual tracking lookup by support or customers - fulfillment-provider tracking data without delivery-status automation --- ## Shipping Statuses The MCP overview identifies common Shipping status values such as: ```text Shipped Not Shipped Merged Delivered Error ``` Related status fields can include: | Field | Meaning | |---|---| | `is_shipped` / shipped status | Indicates that the shipment has shipped. | | `is_delivered` / delivered status | Indicates that the shipment has delivered. | | `is_merged` | Indicates that the shipment was merged with another fulfillment shipment. | | `is_merged_with` / `has_merged_with` | Identifies related merged shipment IDs. | A shipment in `Error` status or a shipment where fulfillment was not notified should be treated as an operations/support issue. --- ## Editing Shipping Records Shipping records can be edited from the web app or through the API/MCP operations. Common edits include: - adding or changing a tracking number - marking the shipment as shipped - marking the shipment as delivered - updating provider or provider method - updating ship-to details In the API/MCP context, `EditShipment` requires the Shipping ID and can include optional fields such as provider, provider method, tracking number, shipped status, delivered status, and ship-to details. Important operational caution: ```text Changes to the ship-to address may update fulfillment where applicable. ``` Do not update ship-to details casually after fulfillment has already been sent to a provider. Address updates can affect fulfillment operations and customer expectations. --- ## Viewing and Searching Shipping In the web app, Shipping records can be viewed under Revenue > Shipping > All Shipping. A specific Shipping record can be opened from search or by clicking the Shipping ID. The details page can show related entities such as sale, product sold, renewals, tax, and other connected records. The MCP overview describes three main operational lookup patterns: | Operation | Best Use | |---|---| | `GetShipment` | Retrieve one shipment when the Shipping ID is known. | | `SearchShipping` | Search for a shipment by customer name, customer email, metadata, or another search term. | | `GetShipments` | Retrieve a small bounded operational list of shipments. | `GetShipments` and `SearchShipping` should not be used for bulk reporting, data mining, or metrics. For reporting, use BigQuery. --- ## Shipping and Customer Support Shipping records are highly useful for customer support because they connect customer, product, sale, fulfillment, tracking, and delivery context. A support workflow may look like: ```text Customer asks about shipment ↓ SearchShipping or GetShipment ↓ Review shipping_status, tracking, ship_to, products, and fulfillment notification ↓ Answer customer or escalate ↓ Send follow-up Email Template if needed ↓ Create note, AI Memo, or support ticket if needed ``` Support teams can use Shipping records to answer questions such as: - Has the item shipped? - What is the tracking number? - Which provider is carrying the package? - Was delivery confirmed? - Which product was shipped? - Was the fulfillment provider notified? - Did a delivery problem occur? - Should the customer receive an update? If tracking is missing, AI or support workflows should say it is not available yet. They should not invent shipment or delivery status. --- ## Shipping and Email Templates Shipping records can power customer-facing and internal Email Templates. Common Shipping-related email triggers include: | Trigger Concept | Common Use | |---|---| | Shipping Item Created | Notify internal operations that a shipment was created. | | Shipping Item Shipped | Send tracking number and tracking URL to the customer. | | Shipping Item Delivered | Send delivery confirmation or post-delivery follow-up when delivery status is available. | | Shipping Item Voided | Notify support or operations that a shipment was cancelled or should not be fulfilled. | Shipping-related Email Templates can use shipment input data such as customer details, ship-to address, products, tracking number, tracking URL, provider, provider method, and shipping status. Use shipped emails for tracking updates. Use delivered emails only when RevCent actually has delivered status available. --- ## Shipping and AI Assistants AI Assistants can review Shipping records when the workflow requires reasoning, prioritization, summarization, or branching. Useful AI Assistant use cases include: - review shipments still `Not Shipped` after a delay - summarize shipping status for support - identify fulfillment-notification failures - create AI Memos for urgent shipment issues - review shipments in `Error` status - monitor subscription refill shipments - monitor trial-related shipments - trigger a Function for supplemental external workflows - recommend support action for delayed or delivery-problem shipments Recommended pattern: ```text Shipping event occurs ↓ AI Assistant starts with filters and max-runs-per-item protection ↓ Assistant reviews Shipping record context ↓ Assistant branches based on status, tracking, provider, fulfillment notification, product, country, or metadata ↓ Assistant records outcome with note, AI Memo, Function, metadata, or Email Template ``` AI Assistants should not be used to duplicate the normal fulfillment-provider notification that RevCent already performs through Fulfillment Accounts. --- ## Shipping and AI Voice Agents AI Voice Agents can help customers and support teams with shipment-status questions. Common voice use cases include: - “Where is my order?” - “Has my item shipped?” - “What is my tracking number?” - “Was my package delivered?” - “My package was not received.” - “Can I update my shipping address?” An AI Voice Agent should retrieve or search the relevant Shipping record, explain only the status that exists in RevCent, and escalate when tracking is missing, delivery visibility is not configured, fulfillment was not notified, or the shipment has an error. Voice Agents should not invent tracking or delivery status. --- ## Shipping and Chargeback Evidence Shipping records can support chargeback evidence when a dispute involves product delivery. Useful Shipping evidence can include: - ship-to address - provider - provider method - tracking number - tracking URL - shipped date - delivered date when available - products shipped - fulfillment account context - customer notifications For product-not-received disputes, shipping and delivery evidence can help the business show whether the product was shipped or delivered. --- ## Shipping and Third-Party Shops Third-party shops, especially WooCommerce stores, require careful shipping-method mapping. A remote shop may have its own shipping methods. RevCent needs those remote methods to be mapped to RevCent provider and provider method values so shipments created from remote-shop orders have the correct shipping context. MCP guidance for WooCommerce shops: ```json { "user_shop_id": "XXXXXXXXXXXXXXXXXXXX", "remote_data": ["shipping_methods"] } ``` The `remote_data.shipping_methods` option retrieves shipping methods from the remote WooCommerce shop. The AI/MCP client should compare remote methods against the methods saved in the RevCent shop configuration and ensure active remote methods are mapped correctly. Incorrect mapping can cause fulfillment, carrier, provider method, tracking, or support context issues. --- ## Shipping and Reporting Shipping records are available in BigQuery through the `shipping` table. Use BigQuery for shipping metrics, trends, aggregation, and operational reporting. Do not use `GetShipments` or `SearchShipping` for reporting or bulk discovery. Useful reporting questions include: - How many shipments were created by day? - How many shipments are `Not Shipped`, `Shipped`, `Delivered`, `Merged`, or `Error`? - Which Fulfillment Accounts have the most shipments? - Which shipments were not sent to fulfillment? - Which providers and methods are used most often? - What is shipping revenue, cost, and margin? - Which campaigns, shops, products, or product groups generate the most shipments? - How many subscription renewal shipments are created? - How many trial shipments are created? - Which shipments were refunded? - Which shipments are connected to chargebacks? - How long does it take shipments to move from created to shipped or delivered? Reference the table as: ```sql `revcent.user.shipping` ``` --- ## BigQuery Table Context The `shipping` table contains all shipments created. A shipment is created when a shippable product is sold to a customer in a sale, subscription renewal, or trial expiration. Important fields include: | Field Area | Fields | |---|---| | Identity | `created_at`, `id`, `live_mode` | | Amounts | `amount_original_total`, `amount_total`, `amount_net`, `amount_gross`, `amount_fees`, `amount_remaining`, `amount_discounted`, `amount_refunded`, `amount_to_salvage`, `cost`, `iso_currency` | | Customer | `customer`, `customer_detailed`, `ship_to` | | Shipping status | `shipping_status`, `ship_date`, `delivered_date`, `provider`, `provider_method`, `provider_tracking` | | Fulfillment | `fulfillment_account`, `fulfillment_account_notified`, `fulfillment_account_notified_date` | | Merge status | `is_merged`, `has_merged`, `is_merged_with`, `has_merged_with` | | Business context | `campaign`, `third_party_shop`, `payment_type`, `api_call` | | Products | `products_detailed`, `products`, `product_sale` | | Related commerce records | `sale`, `subscription`, `subscription_renewal`, `trial`, `salvage_transaction`, `transaction`, `offline_payment`, `check`, `tax`, `pending_refund`, `chargeback`, `paypal_transaction` | | Metadata | `metadata` | These fields make Shipping records useful for both operational support and financial/fulfillment analysis. --- ## Example BigQuery Uses Shipping status counts: ```sql SELECT shipping_status, COUNT(*) AS shipments FROM `revcent.user.shipping` GROUP BY shipping_status ORDER BY shipments DESC; ``` Fulfillment notification issues: ```sql SELECT id, created_at, fulfillment_account, shipping_status, fulfillment_account_notified FROM `revcent.user.shipping` WHERE fulfillment_account IS NOT NULL AND fulfillment_account_notified = FALSE ORDER BY created_at DESC; ``` Shipping revenue, cost, and margin: ```sql SELECT DATE(created_at) AS shipment_date, SUM(amount_gross) AS shipping_gross, SUM(cost) AS shipping_cost, SUM(amount_gross - cost) AS estimated_shipping_margin FROM `revcent.user.shipping` GROUP BY shipment_date ORDER BY shipment_date DESC; ``` Shipments connected to chargebacks: ```sql SELECT id, created_at, shipping_status, provider, provider_method, provider_tracking, chargeback FROM `revcent.user.shipping` WHERE chargeback IS NOT NULL ORDER BY created_at DESC; ``` --- ## Common Mistakes to Avoid Do not: - treat Shipping as the same thing as a Shipping Profile - treat Shipping as the same thing as a Fulfillment Account - sell a shippable product without a valid Fulfillment Account - assign live shippable products to a disabled Fulfillment Account - create Shipping Profile rates without usable qualifiers - assume every trial product ships immediately - forget that subscription renewals may require recurring shipments - use Functions or external systems to duplicate RevCent's normal fulfillment notification - assume a tracking number means the package was delivered - send delivery confirmation when delivered status is not known - let AI Assistants or AI Voice Agents invent shipment or delivery status - ignore WooCommerce or remote-shop shipping-method mapping - use `GetShipments` or `SearchShipping` for reporting or bulk data mining - update ship-to details without considering fulfillment impact - forget to check whether the Fulfillment Account was notified --- ## Summary Shipping in RevCent is the item-level record that represents a shipment created from shippable commerce activity. A Shipping record can be created from an initial sale, processed pending sale, subscription renewal, trial event, shippable bundle, or connected third-party shop order. It connects customer details, ship-to details, products, sale context, fulfillment context, provider/method, tracking, delivery status, refunds, chargebacks, metadata, automation, and reporting. The most important ecosystem distinction is: ```text Shipping Profile = reusable shipping-rate and rule feature Fulfillment Account = reusable fulfillment provider connection feature Shipping = individual shipment item created from commerce activity ``` For a physical-product business, Shipping records are critical because they connect RevCent's revenue lifecycle to fulfillment, customer support, shipping notifications, delivery visibility, chargeback evidence, AI workflows, and BigQuery reporting. --- Document Parent Directory * [Items](https://revcent.com/documentation/markdown/ecosystem/item/index.md) - Non-technical markdown documentation for items within the RevCent ecosystem. An item is an entity that is spawned as a result of a feature or operation conducted within the RevCent ecosystem.