New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee


  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

AI in Chargebee


  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model Context Protocol)

Developer Resources


  • Developer Resources Overview
  • Articles and FAQ

Product Catalog


  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions


  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers


  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Entitlements


  • Entitlements Overview
  • Features Overview
  • Feature Management
  • Managing Product Entitlements
  • Subscription Entitlements
  • Customer Entitlements
  • Grandfathering Entitlements
  • Articles and FAQ

Usage Based Billing


  • Understanding Usages
  • Setting up Usage Based Billing
  • Usage Alerts
  • Metered Billing
  • Articles and FAQ

Chargebee CPQ


  • Chargebee CPQ
  • Chargebee CPQ for Salesforce
  • Chargebee CPQ for HubSpot

Invoices, Credit Notes, and Quotes


  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes


  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities


  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Pricing Table
  • Managing Payments with Chargebee.js
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Approvals
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Multi Business Entity


  • Multi Business Entity Overview
  • Customer Transfer Overview
  • Articles and FAQ

Mobile Subscriptions


  • Overview
  • Omnichannel Subscriptions
  • Omnichannel One-Time Orders
  • Mobile Subscriptions (Legacy)

Reports and Analytics


  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations


  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • eInvoicing
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Ecommerce Management
    • ShipStation
      • ShipStation Integration: Field-Mapping
    • BigCommerce
  • Articles and FAQ

Data Privacy & Security


  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations


  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  2. Integrations
  3. Ecommerce Management
  4. ShipStation
  5. ShipStation Integration: Field-Mapping
  1. Billing
  2. Integrations
  3. Ecommerce Management
  4. ShipStation
  5. ShipStation Integration: Field-Mapping

ShipStation Integration: Field-Mapping

The following table lists the fields that are mapped between Chargebee and ShipStation when the integration is enabled and orders are synced.

Serial #Chargebee fieldShipStation field
1document_numberorderNumber
2reference_idorderKey
3order_dateorderDate
4paid_atpaymentDate
5fulfillment_statusorderStatus
6statusNo direct mapping. Field value in Chargebee is assigned based on the value of order status in ShipStation. See this table.
7shipped_atshipDate
8delivered_atfullfillments[deliveryDate]
9tracking_idshipments[trackingNumber]
10batch_idshipments[batchNumber]
11shipment_carriershipments[carrierCode]
12customer[first_name] and customer[last_name]customerUsername
13customer[email]customerEmail
14amount_paidamountPaid
15taxtaxAmount
16noteinternalNotes
17order_line_items[id]OrderItem[lineItemKey]
18order_line_items[description]OrderItem[name]
19You can optionally have custom fields plan price[cf_inv_sku] or addon price[cf_inv_sku] or charge price[cf_inv_sku]. These fields are mapped to ShipStation depending on whether order_line_items[entityType] is plan or addon or charge respectively. Within the Custom fields, Field Label and API Name must be [cf_inv_sku]. Otherwise, order_line_items[sku] is mapped to ShipStation.OrderItem[sku]
20order_line_items[fulfillment_quantity]OrderItem[quantity]
21order_line_items[unit_price]OrderItem[unitPrice]
22order_line_items[tax_amount]OrderItem[taxAmount]
23billing_address[first_name] & billing_address[last_name]billTo[name]
24billing_address[company]billTo[company]
25billing_address[line1]billTo[street1]
26billing_address[line2]billTo[street2]
27billing_address[line3]billTo[street3]
28billing_address[city]billTo[city]
29billing_address[state]billTo[state]
30billing_address[zip]billTo[postalCode]
32billing_address[country]billTo[country]
32billing_address[phone]billTo[phone]
33shipping_addressshipTo (field mapping is same as billing_address to billTo mapping)

Was this article helpful?