Platform Order Details Reference
Contents
- 1. How to read this reference
- 2. Shopee
- 3. 91APP
- 4. Shopify
- 5. Shopline
- 6. WooCommerce
- 7. Liteshop
- 8. BVSHOP
- 9. FreeStore
- 10. Cyberbiz
- 11. EasyStore
- 12. 1shop
- 13. Coupang
- 14. Ruten
- 15. Yahoo SCM
- 16. MO Plus
- 17. PChome
- 18. ETMall
- 19. momo
- 20. FAQ
- 21. Related features
1. How to read this reference
Platform order details are the amount breakdown and reconciliation data the platform provides beyond the order itself: item discounts, vouchers, coin redemptions, commissions and fees, the expected payout, the payment method, package numbers and so on. The system fetches them together with the order, so you do not have to look each order up in the platform's back office when reconciling.
The same fields appear in three places, and this page is the reference for their names and meaning:
| Where | Notes |
|---|---|
| The "Platform Details" tab on the order detail page | Available to both the warehouse and the merchant back office, read-only; loaded only when you open the tab. Summary cards at the top depend on the platform (see each platform section); below them, fields follow categories shared by every platform (Order amounts, Seller settlement, Payment, Tax & invoice, Reconciliation keys, Cost); categories the platform has no fields for are hidden. Hover over the ⓘ next to a field name to see what it means, which platform API it comes from and the response field |
| Partners API | From version 2026-09, the single-order endpoint (GET /orders/{id}) and the order created / shipped / cancelled webhooks include platform_detail; order lists do not |
| This page | One section per platform, listing each field, its name, the original platform field and when it has a value |
How the data is updated:
- Updated with every order fetch: each fetch re-reads the platform data and writes only when the content changed, also updating the order's last-updated time. Item lines, fulfillments and inventory are not touched, so orders already being worked on keep updating.
- When the platform provides no details or they have not been fetched yet, the tab shows "No platform data" and the Partners API returns
null; the next fetch fills them in. - De-identified orders are no longer updated.
- Amounts always have exactly two decimal places and keep the platform's sign (see each platform's notes).
- Only the platforms listed on this page have this tab; orders from other platforms, manually created or imported orders, and duplicated orders do not show it.
2. Shopee
Shopee fields fall into four categories: Order amounts, Seller settlement, Payment and Reconciliation keys; Shopee has no tax & invoice or cost fields. Amount and settlement fields come from Shopee's escrow detail and payment and reconciliation fields from the order detail; the "Shopee field" column below names each field's source API.
- Updated only while the order is "ready to ship": the system only fetches Shopee orders that are ready to ship, so the final settlement Shopee makes at payout after shipment is not written back. Income and fees are Shopee's pre-shipment estimates and may differ from the actual payout.
- Signs: discount amounts in Order amounts are positive, except "Buyer payment details (buyer view, deductions are negative)", which is the buyer's view: there discounts are negative, and it is collapsed by default on screen.
- Shipping fee: "Shipping fee" in "Buyer payment details (buyer view, deductions are negative)" is written to the order's shipping fee when the order is created. If it was not available at creation, it is filled in the first time it arrives and only while the order's shipping fee is still empty; an existing shipping fee is never overwritten.
- Payout time is not provided: Shopee only has a payout time after the payout, which is post-shipment settlement data and currently out of scope.
Order amounts
Available once Shopee returns the escrow detail. Values are Shopee's estimates before shipment; the final settlement after payout is not written back.
| Field | Name | Shopee field | When available |
|---|---|---|---|
| Item amounts | |||
order_income.order_original_price | Original item total Total original price of the items before any discount. | order_income.order_original_priceEscrow detail( get_escrow_detail_batch) | See category note |
order_income.seller_discount | Seller item discount Item discount funded by the seller. | order_income.seller_discountEscrow detail( get_escrow_detail_batch) | See category note |
order_income.shopee_discount | Shopee discount Item discount subsidised by Shopee. | order_income.shopee_discountEscrow detail( get_escrow_detail_batch) | See category note |
order_income.order_discounted_price | Discounted item total Total item price after seller and Shopee item discounts, excluding vouchers and shipping. | order_income.order_discounted_priceEscrow detail( get_escrow_detail_batch) | See category note |
| Vouchers & discounts | |||
order_income.voucher_from_seller | Seller voucher Amount covered by seller vouchers (positive number). | order_income.voucher_from_sellerEscrow detail( get_escrow_detail_batch) | See category note |
order_income.voucher_from_shopee | Shopee voucher Amount covered by Shopee vouchers (positive number). | order_income.voucher_from_shopeeEscrow detail( get_escrow_detail_batch) | See category note |
order_income.coins | Shopee coins Amount the buyer paid with Shopee coins (positive number). | order_income.coinsEscrow detail( get_escrow_detail_batch) | See category note |
order_income.seller_coin_cash_back | Seller coin cashback Shopee coin cashback funded by the seller. | order_income.seller_coin_cash_backEscrow detail( get_escrow_detail_batch) | See category note |
order_income.credit_card_promotion | Credit card promotion Discount from bank credit card promotions. | order_income.credit_card_promotionEscrow detail( get_escrow_detail_batch) | See category note |
order_income.seller_voucher_code | Seller voucher codes Seller voucher codes used by the buyer. | order_income.seller_voucher_codeEscrow detail( get_escrow_detail_batch) | Available only when the buyer used a seller voucher code. |
order_income.order_seller_discount | Seller order discount Order-level discount funded by the seller (the legacy WMS "seller discount" field). | order_income.order_seller_discountEscrow detail( get_escrow_detail_batch) | See category note |
| Shipping | |||
order_income.buyer_paid_shipping_fee | Buyer-paid shipping fee Shipping fee paid by the buyer. | order_income.buyer_paid_shipping_feeEscrow detail( get_escrow_detail_batch) | See category note |
order_income.buyer_total_amount | Buyer total amount Total amount paid by the buyer. | order_income.buyer_total_amountEscrow detail( get_escrow_detail_batch) | See category note |
| Buyer payment details (buyer view, deductions are negative) | |||
buyer_payment_info.shipping_fee | Shipping fee Shipping fee the buyer paid at checkout; also written to the order's shipping fee when the order is created. | buyer_payment_info.shipping_feeEscrow detail( get_escrow_detail_batch) | Available once Shopee returns the escrow detail. |
buyer_payment_info.seller_voucher | Seller voucher Seller voucher deduction as seen by the buyer (negative number). | buyer_payment_info.seller_voucherEscrow detail( get_escrow_detail_batch) | Available once Shopee returns the escrow detail. |
buyer_payment_info.shopee_voucher | Shopee voucher Shopee voucher deduction as seen by the buyer (negative number). | buyer_payment_info.shopee_voucherEscrow detail( get_escrow_detail_batch) | Available once Shopee returns the escrow detail. |
buyer_payment_info.shopee_coins_redeemed | Shopee coins redeemed Shopee coins redeemed as seen by the buyer (negative number). | buyer_payment_info.shopee_coins_redeemedEscrow detail( get_escrow_detail_batch) | Available once Shopee returns the escrow detail. |
Seller settlement
Available once Shopee returns the escrow detail. Values are Shopee's estimates before shipment; the final settlement after payout is not written back.
| Field | Name | Shopee field | When available |
|---|---|---|---|
| Platform fees (deducted from payout) | |||
order_income.commission_fee | Commission fee Commission fee charged by Shopee. | order_income.commission_feeEscrow detail( get_escrow_detail_batch) | See category note |
order_income.seller_transaction_fee | Seller transaction fee Transaction fee charged to the seller. | order_income.seller_transaction_feeEscrow detail( get_escrow_detail_batch) | See category note |
order_income.credit_card_transaction_fee | Credit card transaction fee Credit card transaction fee. | order_income.credit_card_transaction_feeEscrow detail( get_escrow_detail_batch) | See category note |
order_income.service_fee | Service fee Other service fees (e.g. free shipping or coin cashback programme fees). | order_income.service_feeEscrow detail( get_escrow_detail_batch) | See category note |
order_income.order_ams_commission_fee | AMS commission fee Affiliate marketing solution (AMS) commission fee. | order_income.order_ams_commission_feeEscrow detail( get_escrow_detail_batch) | See category note |
order_income.buyer_transaction_fee | Buyer transaction fee Transaction fee charged to the buyer. | order_income.buyer_transaction_feeEscrow detail( get_escrow_detail_batch) | See category note |
| Shipping settlement | |||
order_income.shopee_shipping_rebate | Shopee shipping rebate Shipping fee rebate from Shopee. | order_income.shopee_shipping_rebateEscrow detail( get_escrow_detail_batch) | See category note |
order_income.seller_shipping_discount | Seller shipping discount Shipping discount funded by the seller. | order_income.seller_shipping_discountEscrow detail( get_escrow_detail_batch) | See category note |
order_income.final_shipping_fee | Seller-borne shipping fee Final shipping fee borne by the seller. | order_income.final_shipping_feeEscrow detail( get_escrow_detail_batch) | See category note |
order_income.reverse_shipping_fee | Reverse shipping fee Reverse (return) shipping fee. | order_income.reverse_shipping_feeEscrow detail( get_escrow_detail_batch) | See category note |
order_income.escrow_amount | Escrow amount Amount Shopee expects to release to the seller after all fees. | order_income.escrow_amountEscrow detail( get_escrow_detail_batch) | See category note |
Payment
Available as soon as the order is fetched into Vanta.
| Field | Name | Shopee field | When available |
|---|---|---|---|
order_detail.payment_method | Payment method Payment method as returned by Shopee (e.g. Cash on Delivery, Credit Card). | payment_methodOrder detail( get_order_detail) | See category note |
order_detail.pay_time | Payment time Time the buyer paid. | pay_timeOrder detail( get_order_detail) | Available after the buyer pays; empty for cash-on-delivery orders until pickup. |
order_detail.cod | Cash on delivery Whether the order is cash on delivery. | codOrder detail( get_order_detail) | See category note |
Reconciliation keys
Available as soon as the order is fetched into Vanta.
| Field | Name | Shopee field | When available |
|---|---|---|---|
order_detail.order_sn | Shopee order number Shopee order number, used to match the order in Shopee Seller Centre. | order_snOrder detail( get_order_detail) | See category note |
order_detail.package_number | Package numbers Shopee package numbers. | package_list[].package_numberOrder detail( get_order_detail) | Available once Shopee assigns logistics; lists every package in Shopee's order when the order ships in several packages. |
order_detail.group_shipment_id | Group shipment IDs Shopee group shipment IDs. | package_list[].group_shipment_idOrder detail( get_order_detail) | Available only for packages Shopee ships as a group shipment. |
order_detail.shipping_carrier | Shipping carrier Logistics carrier assigned by Shopee. | shipping_carrierOrder detail( get_order_detail) | Available once Shopee assigns the logistics channel. |
3. 91APP
91APP fields fall into five categories: Order amounts, Payment, Tax & invoice, Reconciliation keys and Cost; 91APP has no seller settlement fields. The summary cards at the top show the amount paid and the payment type. Apart from the invoice carrier, every field comes from the 91APP order query (SalesOrder/Get).
- A 91APP order is made of sub-orders: one Vanta order maps to one 91APP master order (TM), and each item under it is a sub-order (TS). Sub-order amounts (amount paid, item total, discounts, cost) are summed over the sub-orders in this Vanta order, the same set used for the order total; text fields such as sub-order numbers, shipping order codes and tax types list the de-duplicated values of all sub-orders.
- Unit prices are not provided: summing sub-order unit prices (
Price,Cost) is meaningless, so they are left out; use the item total and total cost instead. - Shipping fee: "Shipping fee" is written to the order's shipping fee when the order is created. For orders fetched before this, it is filled in the first time the details arrive and only while the order's shipping fee is still empty; an existing shipping fee is never overwritten.
- Invoice tax ID and title go on the order itself: they come from the 91APP not-yet-invoiced order query (
NotIssueInvoiceSalesOrder/Get) and are written to the order's buyer tax ID and buyer name (only fields that are still empty; when both are present the buyer type is set to business). They do not appear on this tab. The carrier type and code are listed under Tax & invoice. - A failed invoice query does not block the order: the order is created as usual with empty carrier fields, which are filled on the next fetch; once obtained they are not queried again.
- Field meanings follow 91APP's raw values: 91APP only documents response samples without field descriptions, so values are stored as returned without further interpretation (for example the tax type and installment values).
Order amounts
Available as soon as the order is fetched into Vanta; sub-order amounts are summed over the sub-orders in this Vanta order.
| Field | Name | 91APP field | When available |
|---|---|---|---|
| Item amounts | |||
sales_order.TotalPrice | Item total Sum of TotalPrice over the sub-orders (91APP does not document the field; raw values are summed). | Data.List[].TotalPriceOrder query( Get) | Available as soon as the order is fetched into Vanta. |
| Discounts | |||
sales_order.TotalDiscount | Total discount Sum of TotalDiscount over the sub-orders (91APP does not document the field; raw values are summed). | Data.List[].TotalDiscountOrder query( Get) | Available as soon as the order is fetched into Vanta. |
sales_order.PromotionDiscount | Promotion discount Sum of PromotionDiscount over the sub-orders (91APP does not document the field; raw values are summed). | Data.List[].PromotionDiscountOrder query( Get) | Available as soon as the order is fetched into Vanta. |
sales_order.ECouponDiscount | Coupon discount Sum of ECouponDiscount over the sub-orders (91APP does not document the field; raw values are summed). | Data.List[].ECouponDiscountOrder query( Get) | Available as soon as the order is fetched into Vanta. |
sales_order.LoyaltyPointDiscount | Loyalty point discount Sum of LoyaltyPointDiscount over the sub-orders (91APP does not document the field; raw values are summed). | Data.List[].LoyaltyPointDiscountOrder query( Get) | Available as soon as the order is fetched into Vanta. |
sales_order.AdditionalDiscount | Additional discount Sum of AdditionalDiscount over the sub-orders (91APP does not document the field; raw values are summed). | Data.List[].AdditionalDiscountOrder query( Get) | Available as soon as the order is fetched into Vanta. |
| Shipping | |||
sales_order.TMShippingFee | Shipping fee Order (TM) shipping fee as returned by 91APP (TMShippingFee); also written to the order's shipping fee when the order is created. | Data.List[].TMShippingFeeOrder query( Get) | Available as soon as the order is fetched into Vanta. |
sales_order.TMShippingFeeTotalDicount | Shipping fee discount Order (TM) shipping fee discount as returned by 91APP (TMShippingFeeTotalDicount; spelling follows 91APP). | Data.List[].TMShippingFeeTotalDicountOrder query( Get) | Available as soon as the order is fetched into Vanta. |
sales_order.TotalPayment | Amount paid Sum of TotalPayment over the sub-orders (91APP does not document the field; raw values are summed). Excludes the order shipping fee. | Data.List[].TotalPaymentOrder query( Get) | Available as soon as the order is fetched into Vanta. |
Payment
Available as soon as the order is fetched into Vanta.
| Field | Name | 91APP field | When available |
|---|---|---|---|
sales_order.OrderPayType | Payment type Payment type as returned by 91APP (e.g. CreditCardOnce, StorePay, ATM). | Data.List[].OrderPayTypeOrder query( Get) | See category note |
sales_order.PayTypeDetailsPayType | Payment detail types Pay types in the sub-orders' payment details (PayTypeDetails), de-duplicated. | Data.List[].PayTypeDetails[].PayTypeOrder query( Get) | See category note |
sales_order.InstallmentDef | Installment setting Installment setting as returned by 91APP (values are not documented). | Data.List[].InstallmentDefOrder query( Get) | Available only when 91APP returns installment information. |
Tax & invoice
The tax type is available as soon as the order is fetched; carrier details come from the 91APP not-yet-invoiced order API and are filled on the next fetch if that call fails.
| Field | Name | 91APP field | When available |
|---|---|---|---|
sales_order.TaxTypeDef | Tax type Tax types of the sub-orders as returned by 91APP (e.g. Taxable; values are not documented), de-duplicated. | Data.List[].TaxTypeDefOrder query( Get) | Available as soon as the order is fetched into Vanta. |
invoice.CarrierType | Carrier type Invoice carrier type as returned by 91APP (values are not documented). | Data.List[].CarrierTypeNot-yet-invoiced order query( Get) | Available once the 91APP not-yet-invoiced order API responds; filled on the next fetch if the call fails, and not queried again once obtained. |
invoice.CarrierCode | Carrier code Invoice carrier code; cleared when the order is de-identified. | Data.List[].CarrierCodeNot-yet-invoiced order query( Get) | Available once the 91APP not-yet-invoiced order API responds; filled on the next fetch if the call fails, and not queried again once obtained. |
Reconciliation keys
Available as soon as the order is fetched into Vanta.
| Field | Name | 91APP field | When available |
|---|---|---|---|
sales_order.TGCode | Cart number 91APP shopping cart number. | Data.List[].TGCodeOrder query( Get) | See category note |
sales_order.TMCode | Master order number 91APP master order number, used to match the order in the 91APP back office. | Data.List[].TMCodeOrder query( Get) | See category note |
sales_order.TSCode | Sub-order numbers 91APP order numbers of the sub-orders in this Vanta order. | Data.List[].TSCodeOrder query( Get) | See category note |
sales_order.ShippingOrderCode | Shipping order codes 91APP shipping order codes, de-duplicated. | Data.List[].ShippingOrderCodeOrder query( Get) | Available once 91APP creates the shipping order. |
sales_order.OrderSource | Order source Order source as returned by 91APP (e.g. 官網(Mobile)). | Data.List[].OrderSourceOrder query( Get) | See category note |
sales_order.OrderReceiverStoreName | Pickup store Pickup store name. | Data.List[].OrderReceiverStoreNameOrder query( Get) | Available only for convenience-store pickup orders. |
sales_order.PayTypeDetailsOrderCode | Payment order codes OrderCode values in the sub-orders' payment details (PayTypeDetails), de-duplicated (the field is not documented). | Data.List[].PayTypeDetails[].OrderCodeOrder query( Get) | Available only when 91APP payment details carry an order code. |
Cost
Available as soon as the order is fetched into Vanta; summed over the sub-orders in this Vanta order.
| Field | Name | 91APP field | When available |
|---|---|---|---|
sales_order.TotalCost | Total cost Sum of TotalCost over the sub-orders (91APP does not document the field; raw values are summed). | Data.List[].TotalCostOrder query( Get) | Available as soon as the order is fetched into Vanta. |
4. Shopify
Shopify has fields in all six categories: Order amounts, Seller settlement, Payment, Tax & invoice, Reconciliation keys and Cost. All of them come from the same Shopify order API used to fetch orders; the summary cards at the top are "Order total", "Financial status" and "Payment gateways".
- Amounts are in the shop currency: Shopify provides both the shop currency and the buyer's checkout currency; only the shop currency is stored.
- Updated with each order fetch: the system only imports Shopify orders that are paid and unfulfilled, and updates the details each time it fetches them. Once an order is fulfilled in Shopify it is no longer fetched, so later refunds and fulfillments are not added.
- Shipping: "Total shipping" is also the order's shipping fee; Shopify does not document whether shipping discounts are deducted from it. The amount after shipping discounts is "Discounted shipping lines total" (how the legacy WMS calculated shipping).
- Seller settlement only has transaction fees: only Shopify Payments transactions carry fees. The Shopify Payments payout net amount and payout batch need a separate query and are not provided yet.
- Cost: the total is calculated only when every line item has a unit cost in Shopify; if any line item has none, it is left empty rather than adding up only some items. The cost is what is set in Shopify when the order is fetched, not the cost when the order was placed.
- Fields with several values: transaction, tax line, fulfillment and refund fields can hold several values per order, listed in Shopify's order. A missing value shows -, so fields in a group (for example a transaction's gateway and processing time) have the same count and the same position is the same entry. "Tax amounts" lists one row per tax line under the field name, with the tax name on the left ("Item n" when there is none) and the amount on the right.
- Limits on totals: order fetching reads the first 50 line items, 5 shipping lines and 20 transactions of each order; when an order has more line items or shipping lines, or 20 or more transactions, the related total is left empty instead of adding up only part of it.
- Returns are not provided: Shopify returns need an extra permission and are out of scope for now.
Order amounts
| Field | Name | Shopify field | When available |
|---|---|---|---|
| Item amounts | |||
order.original_total_sum | Items original price total Sum of each line item's originalTotalSet (total price when the order was created, before discounts), including items that do not require shipping; Shopify orders have no pre-discount line item total field. Empty when the order has more than 50 line items (order fetching reads only the first 50). | lineItems.nodes[].originalTotalSet.shopMoney.amountOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
| Discounts and credits | |||
order.total_discounts | Total discounts Total amount discounted on the order, before returns. | totalDiscountsSet.shopMoney.amountOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
order.discount_codes | Discount codes Discount codes used for the order. | discountCodesOrder details( GraphQL Admin API orders) | Available only when the buyer used discount codes; an order can have several. |
transactions.store_credit_amount_sum | Store credit used total Sum of the amountSet of each successful SALE and CAPTURE transaction whose gateway is shopify_store_credit; an AUTHORIZATION that has not been captured is not counted. Shopify orders have no store credit total field. Empty when the order has 20 or more transactions (order fetching reads only the first 20). | transactions[].amountSet.shopMoney.amountOrder transactions( GraphQL Admin API orders) | Available only when the buyer paid with Shopify store credit. |
| Shipping | |||
order.total_shipping_price | Total shipping Total shipping cost of the Shopify order (totalShippingPriceSet). Shopify's documentation does not say whether shipping discounts are deducted; the legacy WMS summed each shipping line's discounted price, which is the "Discounted shipping lines total" field (shipping_lines_discounted_price_sum). The order's shipping fee also uses this value. | totalShippingPriceSet.shopMoney.amountOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
order.shipping_lines_discounted_price_sum | Discounted shipping lines total Sum of each shipping line's discountedPriceSet (per Shopify, the shipping price after discounts), which is how the legacy WMS calculated shipping. Unlike "Total shipping", this field is known to have shipping discounts deducted. Empty when the order has more than 5 shipping lines (order fetching reads only the first 5). | shippingLines.nodes[].discountedPriceSet.shopMoney.amountOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
order.total_price | Order total Total price of the order, before returns. | totalPriceSet.shopMoney.amountOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
Seller settlement
Only transactions paid through Shopify Payments carry fees; empty for other payment providers.
| Field | Name | Shopify field | When available |
|---|---|---|---|
transactions.fees_sum | Transaction fees total Sum of fees.amount across every fee of every transaction; only Shopify Payments transactions carry fees, and Shopify orders have no fee total field. The payout net amount is not included. Empty when a fee is in a currency other than the shop currency or the order has 20 or more transactions. | transactions[].fees[].amount.amountOrder transactions( GraphQL Admin API orders) | Available only for transactions paid through Shopify Payments. |
Payment
| Field | Name | Shopify field | When available |
|---|---|---|---|
order.payment_gateway_names | Payment gateways Names of all payment gateways used for the order, as returned by Shopify (merchants can customise them, e.g. shopify_payments, Cash on Delivery). | paymentGatewayNamesOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
order.display_financial_status | Financial status Financial status as shown in Shopify admin (e.g. PAID, PENDING, PARTIALLY_REFUNDED). | displayFinancialStatusOrder details( GraphQL Admin API orders) | Reflects the status at the last fetch only; scheduled fetching covers only paid, unfulfilled Shopify orders, so later refunds and fulfillments update it when the platform sends an order update. |
order.currency_code | Shop currency Shop currency when the order was placed. | currencyCodeOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
transactions.gateway | Transaction gateways Payment gateway of each transaction. | transactions[].gatewayOrder transactions( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta and reflects transactions as of the last fetch; listed in Shopify's transaction order with null where a value is missing, so every field has the same count and the same position is the same transaction. |
transactions.kind | Transaction kinds Kind of each transaction as returned by Shopify (e.g. SALE, AUTHORIZATION, CAPTURE, REFUND). | transactions[].kindOrder transactions( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta and reflects transactions as of the last fetch; listed in Shopify's transaction order with null where a value is missing, so every field has the same count and the same position is the same transaction. |
transactions.status | Transaction statuses Status of each transaction as returned by Shopify (e.g. SUCCESS, PENDING, FAILURE). | transactions[].statusOrder transactions( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta and reflects transactions as of the last fetch; listed in Shopify's transaction order with null where a value is missing, so every field has the same count and the same position is the same transaction. |
transactions.processed_at | Transaction times Time each transaction was processed (ISO 8601, as returned by Shopify). | transactions[].processedAtOrder transactions( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta and reflects transactions as of the last fetch; listed in Shopify's transaction order with null where a value is missing, so every field has the same count and the same position is the same transaction. |
Tax & invoice
| Field | Name | Shopify field | When available |
|---|---|---|---|
order.taxes_included | Taxes included Whether taxes are included in the order subtotal. | taxesIncludedOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
order.total_tax | Total tax Total tax amount, before returns. | totalTaxSet.shopMoney.amountOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
order.tax_lines_rate_percentage | Tax rates (%) Rate of each tax as a percentage, as returned by Shopify. | taxLines[].ratePercentageOrder details( GraphQL Admin API orders) | Available only when the order has tax lines; one entry per tax line in order, with null where there is no value, so the count equals the number of tax lines. |
order.tax_lines_price | Tax amounts Each tax line as its name (title of every taxLines entry; shown as "Item n" when there is none) and amount after discounts and before returns, in tax-line order; a missing or unparsable amount is null. | taxLines[].priceSet.shopMoney.amount(label: taxLines[].title)Order details( GraphQL Admin API orders) | Available only when the order has tax lines; one entry per tax line, in order. |
Reconciliation keys
| Field | Name | Shopify field | When available |
|---|---|---|---|
order.id | Shopify order ID Shopify order ID (GID, e.g. gid://shopify/Order/123), used to match the order in Shopify admin and the API. | idOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
order.name | Shopify order number Shopify order number (e.g. | nameOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
order.source_name | Order source Name of the order source (e.g. web, pos, or a third-party app). | sourceNameOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
order.source_identifier | Source order identifier Unique POS or third-party order identifier. | sourceIdentifierOrder details( GraphQL Admin API orders) | Available only for orders created by POS or a third party. |
order.po_number | PO number Purchase order (PO) number associated with the order. | poNumberOrder details( GraphQL Admin API orders) | Available only when the order has a purchase order number. |
order.total_refunded | Total refunded Total amount refunded on the Shopify order (totalRefundedSet). | totalRefundedSet.shopMoney.amountOrder details( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta; reflects refunds as of the last fetch only. Scheduled fetching covers only unfulfilled Shopify orders, so later refunds (including after shipment) update when the platform sends an order update. |
transactions.id | Transaction IDs Shopify ID of each transaction. | transactions[].idOrder transactions( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta and reflects transactions as of the last fetch; listed in Shopify's transaction order with null where a value is missing, so every field has the same count and the same position is the same transaction. |
fulfillments.id | Shopify fulfillment IDs Shopify fulfillment IDs. | fulfillments[].idOrder fulfillments( GraphQL Admin API orders) | Reflects only the last time the order was fetched. Scheduled fetching covers only unfulfilled Shopify orders, so after fulfillment it updates when the platform sends an order update. |
fulfillments.name | Shopify fulfillment names Human-readable fulfillment references (e.g. | fulfillments[].nameOrder fulfillments( GraphQL Admin API orders) | Reflects only the last time the order was fetched. Scheduled fetching covers only unfulfilled Shopify orders, so after fulfillment it updates when the platform sends an order update. |
fulfillments.tracking_number | Tracking numbers Tracking numbers of the fulfillments. | fulfillments[].trackingInfo[].numberOrder fulfillments( GraphQL Admin API orders) | Reflects only the last time the order was fetched. Scheduled fetching covers only unfulfilled Shopify orders, so after fulfillment it updates when the platform sends an order update. |
fulfillments.tracking_company | Tracking companies Tracking companies of the fulfillments. | fulfillments[].trackingInfo[].companyOrder fulfillments( GraphQL Admin API orders) | Reflects only the last time the order was fetched. Scheduled fetching covers only unfulfilled Shopify orders, so after fulfillment it updates when the platform sends an order update. |
fulfillments.fulfillment_order_id | Shopify fulfillment order IDs Shopify fulfillment order IDs. | fulfillmentOrders.nodes[].idOrder fulfillments( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta. |
fulfillments.fulfillment_order_status | Fulfillment order statuses Status of each Shopify fulfillment order as returned by Shopify (e.g. OPEN, CLOSED). | fulfillmentOrders.nodes[].statusOrder fulfillments( GraphQL Admin API orders) | Available as soon as the order is fetched into Vanta; reflects only the last time the order was fetched. |
refunds.id | Shopify refund IDs Shopify refund IDs. | refunds[].idOrder refunds( GraphQL Admin API orders) | Reflects only the last time the order was fetched; available only if the order already had a refund then. Scheduled fetching covers only unfulfilled Shopify orders, so later refunds (including after shipment) update when the platform sends an order update. |
refunds.created_at | Refund times Creation time of each refund (ISO 8601, as returned by Shopify), with null where a value is missing. | refunds[].createdAtOrder refunds( GraphQL Admin API orders) | Reflects only the last time the order was fetched; available only if the order already had a refund then. Scheduled fetching covers only unfulfilled Shopify orders, so later refunds (including after shipment) update when the platform sends an order update. |
Cost
Available only when every line item has a unit cost set in Shopify.
| Field | Name | Shopify field | When available |
|---|---|---|---|
order.unit_cost_sum | Items cost total Sum of each line item's inventoryItem.unitCost (shop currency) multiplied by the ordered quantity. unitCost is the cost set in Shopify when the order is fetched, not when it was placed; if the merchant changes the cost, it changes the next time the order is fetched. | lineItems.nodes[].variant.inventoryItem.unitCost.amountOrder details( GraphQL Admin API orders) | Available only when every line item has a unit cost in Shopify; empty if any line item has none or the order has more than 50 line items. |
5. Shopline
Shopline fields fall into all six categories: Order amounts, Seller settlement, Payment, Tax & invoice, Reconciliation keys and Cost. All of them come from the order detail the system already fetches; no other API is called. The summary cards at the top show the order total, payment type and payment status.
- Updated only while the order is ready to ship: the system only fetches Shopline orders that are ready to ship and refreshes the details each time; changes on Shopline after the order ships or is cancelled are not written back.
- Seller settlement only has the payment fee: Shopline is a self-hosted store with no platform commission or payout data; "Payment fee" is charged to the buyer and already included in the order total.
- Multiple amounts follow Shopline's order: "Promotion discounts" and "Item cost" list one row per entry under the field name, with the promotion name or SKU on the left ("Item n" when there is none) and the amount on the right. Shopline gives no name for "Custom discounts", so it lists one amount per entry, separated by commas.
- Shipping fee: "Delivery fee" is written to the order's shipping fee when the order is created. Later it is filled in only the first time it arrives and only while the order's shipping fee is still empty; an existing shipping fee is never overwritten.
- Company invoice tax ID and title go to the order's invoice details: when the buyer entered a tax ID and company title on Shopline, they are written to the order's buyer tax ID and name (only fields that are still empty; values the warehouse already entered are kept; the buyer type is set to company when both are present); they are not listed on this tab.
- The carrier number is personal data: "Carrier number" is cleared when the order is de-identified.
Order amounts
Available as soon as the order is fetched into Vanta and updated by later order syncs.
| Field | Name | Shopline field | When available |
|---|---|---|---|
order.subtotal | Item subtotal Price total for all order items. | subtotal.dollarsOrder detail( search) | Available as soon as the order is fetched into Vanta. |
| Discounts and deductions | |||
order.order_discount | Order discount Order discount amount. | order_discount.dollarsOrder detail( search) | Available as soon as the order is fetched into Vanta. |
order.promotion_items | Promotion discounts Each promotion applied to the order, as its name (the promotion's Traditional Chinese title, title_translations.zh-hant; shown as "Item n" when there is none) and discounted amount (discounted_amount of every promotion_items entry). | promotion_items[].discounted_amount.dollars(label: promotion_items[].promotion.title_translations.zh-hant)Order detail( search) | Available only when promotions apply to the order; listed in the order Shopline returns the promotions. |
order.custom_discount_items | Custom discounts Amount of each custom discount (total of every custom_discount_items entry; Shopline docs - Order Custom Discount Item Data), listed in Shopline's order without a name (the docs have no name field), so entries match only by position; null where there is no value. | custom_discount_items[].total.dollarsOrder detail( search) | Available only when the order has custom discounts (common on POS orders); listed in the order Shopline returns them. |
order.user_credit | Store credit Customer store credit applied to the order. | user_credit.dollarsOrder detail( search) | Available as soon as the order is fetched into Vanta. |
order.order_points_to_cash | Points redeemed Amount of member points converted to cash. | order_points_to_cash.dollarsOrder detail( search) | Available as soon as the order is fetched into Vanta. |
order.applied_member_point_redeem_to_cash | Member points redeemed to cash Member points redeemed to cash (raw applied_member_point_redeem_to_cash; Shopline docs do not explain how it differs from order_points_to_cash). | applied_member_point_redeem_to_cash.dollarsOrder detail( search) | Available only when Shopline returns it; the field appears only in Shopline's sample response, not in its field reference. |
| Shipping | |||
order_delivery.total | Delivery fee Delivery fee; also written to the order's shipping fee when the order is created. | order_delivery.total.dollarsOrder detail( search) | Available as soon as the order is fetched into Vanta. |
order.total | Order total Final price total, which includes payment fee and delivery fee. | total.dollarsOrder detail( search) | Available as soon as the order is fetched into Vanta. |
Seller settlement
Available as soon as the order is fetched into Vanta. Shopline only provides the payment fee; it has no platform fee or payout data.
| Field | Name | Shopline field | When available |
|---|---|---|---|
order_payment.payment_fee | Payment fee Fee added for the payment method (charged to the buyer and included in the order total). | order_payment.payment_fee.dollarsOrder detail( search) | Available as soon as the order is fetched into Vanta. |
Payment
Available as soon as the order is fetched into Vanta.
| Field | Name | Shopline field | When available |
|---|---|---|---|
order.currency_iso | Currency Order currency (ISO-4217, e.g. TWD). | currency_isoOrder detail( search) | See category note |
order_payment.payment_type | Payment type Payment type as returned by Shopline (e.g. tw_711_b2c_pay, shopline_payment, bank_transfer). | order_payment.payment_typeOrder detail( search) | See category note |
order_payment.status | Payment status Payment status as returned by Shopline (e.g. pending, completed; Shopline docs do not list every value). | order_payment.statusOrder detail( search) | See category note |
order_payment.paid_at | Paid at Time the payment was completed. | order_payment.paid_atOrder detail( search) | Available after the buyer pays; empty for cash-on-delivery orders until pickup. |
Tax & invoice
Available as soon as the order is fetched into Vanta; invoice numbers appear once Shopline issues the invoice.
| Field | Name | Shopline field | When available |
|---|---|---|---|
order.total_tax_fee | Total tax Total Tax Fee. | total_tax_fee.dollarsOrder detail( search) | Available as soon as the order is fetched into Vanta. |
order.invoices | All invoice numbers Numbers of all invoices issued for the order, including voided ones. | invoices[].invoice_numberOrder detail( search) | Available once Shopline issues invoices; includes voided invoices, listed in the order Shopline returns them. |
invoice.carrier_type | Carrier type Invoice carrier type as returned by Shopline (Shopline docs do not explain the values). | invoice.carrier_typeOrder detail( search) | Available as soon as the order is fetched into Vanta. |
invoice.carrier_number | Carrier number Invoice carrier number (e.g. mobile barcode). | invoice.carrier_numberOrder detail( search) | Available only when the buyer chose an invoice carrier; cleared when the order is de-identified. |
invoice.invoice_number | Invoice number Current invoice number. | invoice.invoice_numberOrder detail( search) | Available once Shopline issues the invoice. |
inclusive_tax_info.fee | Included tax Included tax amount (Shopline docs - Included tax info). | inclusive_tax_info.fee.dollarsOrder detail( search) | Available only when an inclusive tax setting applies to the order. |
inclusive_tax_info.rate | Included tax rate Included tax rate as returned by Shopline. | inclusive_tax_info.rateOrder detail( search) | Available only when an inclusive tax setting applies to the order. |
Reconciliation keys
Available as soon as the order is fetched into Vanta.
| Field | Name | Shopline field | When available |
|---|---|---|---|
order.id | Shopline order ID Shopline order ID (the platform's internal identifier, different from the order number). | idOrder detail( search) | See category note |
order.order_number | Shopline order number Shopline order number; the merchant-defined number when set, otherwise the system-generated number. | order_numberOrder detail( search) | See category note |
order.parent_order_id | Parent order ID Parent order ID after the order is split. | parent_order_idOrder detail( search) | Available only on child orders created by an order split. |
order.child_order_ids | Child order IDs Child order IDs after the order is split. | child_order_idsOrder detail( search) | Available only on parent orders that were split. |
order.created_by | Created by Channel that created the order, as returned by Shopline (e.g. shop, admin, pos, openapi). | created_byOrder detail( search) | See category note |
delivery_data.tracking_number | Tracking number Third-party delivery tracking number from Shopline. | delivery_data.tracking_numberOrder detail( search) | Available once Shopline assigns the logistics. |
order_source.type | Order source Order source type as returned by Shopline (e.g. storefront, FB, LINE, physical store). | order_source.typeOrder detail( search) | Available only when the shop has Shopline's order source feature enabled. |
order_source.id | Order source ID Order source ID. | order_source.idOrder detail( search) | Available only when the shop has Shopline's order source feature enabled. |
Cost
Available as soon as the order is fetched into Vanta; costs are the values the merchant set on Shopline products, 0 when not set.
| Field | Name | Shopline field | When available |
|---|---|---|---|
subtotal_items.cost | Item cost Cost of each order item with the item's SKU, in Shopline's item order (Shopline docs do not say whether it is per unit or per line). | subtotal_items[].cost.dollars(label: subtotal_items[].sku)Order detail( search) | See category note |
6. WooCommerce
WooCommerce fields fall into four categories: Order amounts, Payment, Tax & invoice and Reconciliation keys. All of them come from the order detail the system already fetches; no other API is called. WooCommerce has no Seller settlement or Cost data, so those categories are not shown. The summary cards at the top show the order total, payment method and order status.
- Updated only while the order is processing: the system only fetches WooCommerce orders in processing status and refreshes the details each time; changes on WooCommerce after the order is completed or cancelled are not written back.
- "Item subtotal (sum)" is summed by the system: WooCommerce orders have no item total field, so the system adds up each line item's subtotal before discounts.
- Multiple amounts follow WooCommerce's order: "Coupon discounts", "Tax amounts" and "Shipping tax amounts" list one row per entry under the field name, with the coupon code or tax rate label on the left ("Item n" when there is none) and the amount on the right. "Tax rate codes" lists the codes in tax-rate order, separated by commas; the same position is the same tax rate.
- Shipping fee: "Shipping" is also written to the order's shipping fee and follows WooCommerce's value on every order fetch.
- Payment methods keep the platform values: "Payment method ID" is the payment plugin's code and "Payment method" is the display text configured by the store; both are shown exactly as WooCommerce returns them.
- No tax ID, carrier or invoice number: core WooCommerce has none of these fields; data that invoice plugins store in custom fields does not appear on this tab.
Order amounts
Available as soon as the order is fetched into Vanta and updated by later order syncs.
| Field | Name | WooCommerce field | When available |
|---|---|---|---|
order.line_items_subtotal_sum | Item subtotal (sum) Sum of each line item's subtotal (WooCommerce docs - Line subtotal (before discounts)); WooCommerce orders have no pre-discount item total field. | line_items[].subtotalOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
| Discounts and deductions | |||
order.discount_total | Total discount Total discount amount for the order. | discount_totalOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.coupon_lines_discount | Coupon discounts Each coupon as its code (code of every coupon_lines entry; WooCommerce docs - Coupon code; shown as "Item n" when there is none) and discount amount (WooCommerce docs - Discount total). | coupon_lines[].discount(label: coupon_lines[].code)Order detail( orders) | Available only when the buyer used coupons; listed in the order WooCommerce returns them. |
| Shipping | |||
order.shipping_total | Shipping Total shipping amount for the order; also written to the order's shipping fee. | shipping_totalOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.total | Order total Grand total. | totalOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
Payment
Available as soon as the order is fetched into Vanta; the paid time appears once the buyer pays online.
| Field | Name | WooCommerce field | When available |
|---|---|---|---|
order.payment_method | Payment method ID Payment method ID as returned by WooCommerce (e.g. cod, bacs, ry_ecpay_credit). | payment_methodOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.payment_method_title | Payment method Payment method title as returned by WooCommerce (the display text configured by the store). | payment_method_titleOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.status | Order status Order status as returned by WooCommerce (pending, processing, on-hold, completed, cancelled, refunded, failed or trash). | statusOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.date_paid | Paid at The date the order was paid, as GMT; falls back to the site-timezone date_paid when the GMT value is missing. | date_paid_gmtOrder detail( orders) | Available after the buyer pays online; empty for cash-on-delivery orders before shipment. |
order.currency | Currency Currency the order was created with, in ISO format (e.g. TWD). | currencyOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
Tax & invoice
Available as soon as the order is fetched into Vanta; tax lines appear only when the store has taxes enabled. WooCommerce has no tax ID, invoice carrier or invoice number fields.
| Field | Name | WooCommerce field | When available |
|---|---|---|---|
order.prices_include_tax | Prices include tax True the prices included tax during checkout. | prices_include_taxOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.total_tax | Total tax Sum of all taxes. | total_taxOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.tax_lines_rate_code | Tax rate codes Code of each tax rate (WooCommerce docs - Tax rate code). | tax_lines[].rate_codeOrder detail( orders) | Available only when the store has taxes enabled and the order is taxed; listed in the order WooCommerce returns them, with null where there is no value, so the count equals the number of tax rates. |
order.tax_lines_tax_total | Tax amounts Each tax rate as its label (label of every tax_lines entry; WooCommerce docs - Tax rate label; shown as "Item n" when there is none) and tax total, not including shipping taxes. | tax_lines[].tax_total(label: tax_lines[].label)Order detail( orders) | Available only when the store has taxes enabled and the order is taxed; listed in the order WooCommerce returns them. |
order.tax_lines_shipping_tax_total | Shipping tax amounts Each tax rate as its label (label of every tax_lines entry; shown as "Item n" when there is none) and shipping tax total. | tax_lines[].shipping_tax_total(label: tax_lines[].label)Order detail( orders) | Available only when the store has taxes enabled and the order is taxed; listed in the order WooCommerce returns them. |
Reconciliation keys
Available as soon as the order is fetched into Vanta.
| Field | Name | WooCommerce field | When available |
|---|---|---|---|
order.id | WooCommerce order ID WooCommerce order ID (Unique identifier for the resource; the platform's internal identifier, different from the order number). | idOrder detail( orders) | See category note |
order.number | WooCommerce order number Order number. | numberOrder detail( orders) | See category note |
order.transaction_id | Transaction ID Unique transaction ID. | transaction_idOrder detail( orders) | Available only when the payment plugin records a transaction ID. |
order.created_via | Created via Shows where the order was created, as returned by WooCommerce (e.g. checkout, admin, rest-api). | created_viaOrder detail( orders) | See category note |
7. Liteshop
Liteshop fields fall into all six categories: Order amounts, Seller settlement, Payment, Tax & invoice, Reconciliation keys and Cost. The summary cards at the top show the order total, the payment processing fee and the payment method. Every field comes from the Liteshop order data, in the same response as the order itself; no extra query is made.
- Seller settlement only has the payment processing fee: "Payment processing fee" is the amount and "Payment processing fee rate (%)" is the rate (%, rounded to an integer by Liteshop). Liteshop does not provide platform commission or payout amounts.
- Discounts and return orders are listed one by one: "Discounts" and "Return order refunds" list one row per entry under the field name, with the discount name or return order number on the left and the amount or refund amount on the right.
- Invoice tax ID and buyer go on the order itself: when the invoice has a tax ID and a buyer name, they are written to the order's buyer tax ID and buyer name and the buyer type is set to business (only on orders where all three fields are still empty; filled data is never overwritten). They do not appear on this tab. The invoice number, status, issue date and carrier are listed under Tax & invoice.
- Return orders are not always retrieved: Liteshop only returns them from the single-order query. Vanta's regular fetch uses the order list, so return orders are retrieved only when Liteshop notifies an order change and Vanta re-fetches that order.
- Product cost is listed per item and is for reference only: "Product costs" lists one row per item under the field name, with the SKU on the left and the cost on the right; an item without a cost shows "-", "Item n" is shown when there is no name or SKU, and a long SKU is cut off with "…" (hover to see it in full). Liteshop documents that product cost is not guaranteed to be maintained; values are stored as returned.
Order amounts
Available as soon as the order is fetched into Vanta. Refunds are only retrieved when Liteshop notifies an order change and Vanta re-fetches that order.
| Field | Name | Liteshop field | When available |
|---|---|---|---|
order.subtotal | Subtotal Subtotal (before discounts). | subtotalOrder data( orders) | Available as soon as the order is fetched into Vanta. |
| Discounts | |||
order.order_discount | Total order discount Total order discount. | order_discountOrder data( orders) | Available as soon as the order is fetched into Vanta. |
order.discounts | Discounts Each discount applied, as its name (title of the discounts entry) and amount (amount of the discounts entry). | discounts[].amount(label: discounts[].title)Order data( orders) | Available only when discounts apply to the order; listed in the order Liteshop returns them. |
| Shipping | |||
order.shipping_fee | Shipping fee Shipping fee. | shipping_feeOrder data( orders) | Available as soon as the order is fetched into Vanta. |
order.price | Order total Order total (including shipping fee); the amount actually charged. | priceOrder data( orders) | Available as soon as the order is fetched into Vanta. |
| Refunds | |||
return_orders.returned_prices | Return order refunds Each return order as its number (name) and refund amount (returned_price), in the order Liteshop returns them. | return_orders[].returned_price(label: return_orders[].name)Order details( {order_name}) | Only returned by the single-order query, retrieved when Liteshop notifies an order change and Vanta re-fetches that order; available only when the order has return orders. |
Seller settlement
Available as soon as the order is fetched into Vanta. Only the payment processing fee is provided; Liteshop does not provide platform commission or payout amounts.
| Field | Name | Liteshop field | When available |
|---|---|---|---|
order.payment_charge | Payment processing fee Payment processing fee (amount; the rate is the payment method's extra_charge). | payment_chargeOrder data( orders) | Available as soon as the order is fetched into Vanta. |
payment.extra_charge | Payment processing fee rate (%) Payment processing fee rate (%), rounded to an integer; the fee amount is the order's payment_charge. | payment.extra_chargePayment method( orders) | Available as soon as the order is fetched into Vanta. |
Payment
Available as soon as the order is fetched into Vanta.
| Field | Name | Liteshop field | When available |
|---|---|---|---|
order.payment_status | Payment status Raw payment status (waiting, confirming, paid, cod, refunded). | payment_statusOrder data( orders) | See category note |
order.paid_time | Paid at Payment time. | paid_timeOrder data( orders) | Available once the order is paid; cash-on-delivery orders usually have no value before shipment. |
order.payment_detail_subtypes | Transaction subtypes Raw transaction subtype of every transaction record (payment_detail), e.g. credit. | payment_detail[].subtypeOrder data( orders) | Available only when Liteshop has transaction records for the order. |
order.payment_detail_credit_last_four | Card last four digits Last four digits of the credit card in every transaction record (payment_detail). | payment_detail[].credit_last_fourOrder data( orders) | Available only for credit card payments with transaction records; cleared when the order is de-identified. |
payment.title | Payment method Display name of the payment method. | payment.titlePayment method( orders) | See category note |
payment.code | Payment method code Raw payment method code (e.g. Credit, ATM, CVS COD, Offline COD). | payment.codePayment method( orders) | See category note |
Tax & invoice
Available once Liteshop issues the invoice.
| Field | Name | Liteshop field | When available |
|---|---|---|---|
order.invoice_number | Invoice number Invoice number. | invoice.numberOrder data( orders) | See category note |
order.invoice_status | Invoice status Raw invoice status (new, issuing, waiting, done, cancel_pending, allowance_pending, canceled, allowance). | invoice.statusOrder data( orders) | See category note |
order.invoice_issued_at | Issue date Issue date (YYYY-MM-DD), stored as Liteshop returns it. | invoice.issued_atOrder data( orders) | See category note |
order.invoice_carrier_type | Carrier type Raw carrier type (invoice.carrierType, e.g. cellphone for a mobile barcode). | invoice.carrierTypeOrder data( orders) | See category note |
order.invoice_carrier_id | Carrier ID Carrier ID (invoice.carrierId); cleared when the order is de-identified. | invoice.carrierIdOrder data( orders) | See category note |
Reconciliation keys
Available as soon as the order is fetched into Vanta.
| Field | Name | Liteshop field | When available |
|---|---|---|---|
order.name | Order number Order number, used to match the order in the Liteshop admin. | nameOrder data( orders) | See category note |
order.parent_order_name | Parent order number Parent order number (only on sub-orders created by splitting an order). | parent_order_nameOrder data( orders) | Available only on sub-orders created by splitting an order. |
Cost
Available as soon as the order is fetched into Vanta. Liteshop documents that product cost is not guaranteed to be maintained.
| Field | Name | Liteshop field | When available |
|---|---|---|---|
order.item_costs | Product costs Product cost of each order item with the item's SKU, in Liteshop's item order (Liteshop docs - product cost, not guaranteed to be maintained, integrations should not rely on it; the docs do not say whether it is per unit or per line). | order_items[].cost(label: order_items[].sku)Order data( orders) | Available as soon as the order is fetched into Vanta. |
8. BVSHOP
BVSHOP fields fall into five categories: Order amounts, Seller settlement, Payment, Tax & invoice and Reconciliation keys. All of them come from the order detail the system already fetches; no other API is called. BVSHOP has no cost fields. The summary cards at the top show the order total, payment method and payment status.
- Updated only while the order is unshipped on BVSHOP: the system only fetches BVSHOP orders that have not shipped (paid orders, or unpaid cash-on-delivery orders) and refreshes the details each time; changes after the order ships or is cancelled on BVSHOP are not written back, so cash-on-delivery paid times and invoices issued after shipment never appear.
- Seller settlement only has the fee: BVSHOP provides no platform commission or payout data; "Fee" is already included in the order total (order total = item amount + shipping fee + fee).
- Item subtotal sum: BVSHOP has no item total field, so "Item subtotal sum" adds up each item's subtotal (price × quantity). Bundle amounts sit on the parent item and child items are 0, so nothing is counted twice.
- Status fields show BVSHOP's raw values: "Payment status", "Invoice status" and "Order source" are numeric codes; see the table below for what each value means.
- Shipping fee: the order's shipping fee is already written from BVSHOP's shipping fee when the order is created and on every re-sync; "Shipping fee" here is the same raw value.
- Company invoice tax ID and title go to the order's invoice details: when a BVSHOP order has a tax ID and invoice title, they are written to the order's buyer tax ID and name (only fields that are still empty; values the warehouse already entered are kept; the buyer type is set to company when both are present); they are not listed as separate fields on this tab. For company invoices, "Invoice carrier / donation code" is the tax ID according to BVSHOP docs.
- The invoice carrier is personal data: "Invoice carrier / donation code" is cleared when the order is de-identified.
Order amounts
Available as soon as the order is fetched into Vanta and updated by later order syncs.
| Field | Name | BVSHOP field | When available |
|---|---|---|---|
order.orderItems_totalPrice_sum | Item subtotal sum Sum of each order item's subtotal (BVSHOP docs - subtotal = price × quantity); BVSHOP orders have no item total field. Bundle amounts sit on the parent item and child items are 0, so nothing is counted twice; custom amount items added in the admin or POS (customizeItems) are not included. | orderItems[].totalPriceOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
| Discounts and deductions | |||
order.discountPrice | Discount amount Discount amount (BVSHOP docs do not explain how it relates to the other discount fields). | discountPriceOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.saleDiscountPrice | Promotion discount Promotion discount amount. | saleDiscountPriceOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.couponDiscountPrice | Coupon code discount Coupon code discount amount. | couponDiscountPriceOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.pointDiscountPrice | Store credit Store credit applied to the order. | pointDiscountPriceOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
| Shipping | |||
order.shippingFee | Shipping fee Shipping fee. | shippingFeeOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.totalPrice | Order total Order total = item amount (after discounts) + shipping fee + fee. | totalPriceOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
Seller settlement
Available as soon as the order is fetched into Vanta. BVSHOP only provides the order fee; it has no platform fee or payout data.
| Field | Name | BVSHOP field | When available |
|---|---|---|---|
order.fee | Fee Fee; the order total formula in BVSHOP docs includes it in the order total (order total = item amount + shipping fee + fee). | feeOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
Payment
Available as soon as the order is fetched into Vanta; the paid time appears once the order is paid.
| Field | Name | BVSHOP field | When available |
|---|---|---|---|
order.paymentMethod | Payment method Payment method (the payment method name the merchant set in BVSHOP, e.g. 綠界|信用卡). | paymentMethodOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.paymentStatus | Payment status Payment status as returned by BVSHOP: 1 = unpaid, 2 = paid, -1 = refunded, -4 = expired (BVSHOP order status rules). | paymentStatusOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.paidAt | Paid at Paid time. | paidAtOrder detail( orders) | Available only after the order is paid; the system only fetches unshipped BVSHOP orders, so COD orders paid on delivery never get a value. |
order.isCod | Cash on delivery Whether the order is cash on delivery. | isCodOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
Tax & invoice
Available as soon as the order is fetched into Vanta; the invoice number and issue time appear once BVSHOP issues the invoice.
| Field | Name | BVSHOP field | When available |
|---|---|---|---|
order.invoice_no | Invoice number Invoice number; empty before the invoice is issued. | invoice.noOrder detail( orders) | Available only after BVSHOP issues the invoice; the system only fetches unshipped BVSHOP orders, so invoices issued after shipment never arrive. |
order.invoice_date | Invoice issued at Invoice issue time; empty before the invoice is issued. | invoice.dateOrder detail( orders) | Available only after BVSHOP issues the invoice; the system only fetches unshipped BVSHOP orders, so invoices issued after shipment never arrive. |
order.invoice_status | Invoice status Invoice status as returned by BVSHOP: 0 = not issued, 1 = issued, 2 = voided. | invoice.statusOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.invoice_carrier | Invoice carrier / donation code Depends on the invoice type: the citizen digital certificate barcode, the mobile barcode, the donation code, or the company tax ID for business invoices; empty when there is none. | invoice.carrierOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
Reconciliation keys
Available as soon as the order is fetched into Vanta; tracking and split shipment codes appear once a waybill is created.
| Field | Name | BVSHOP field | When available |
|---|---|---|---|
order.id | BVSHOP order ID Order ID (BVSHOP's internal ID, used when writing tracking numbers back). | idOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.uid | BVSHOP order number Order number (the order number in Vanta). | uidOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.logisticTraceCode | Tracking code Logistics tracking code. | logisticTraceCodeOrder detail( orders) | Available only after a waybill is created. |
order.shippings_shippingCode | Split shipment codes Split shipment codes (shippingCode of every shippings entry); an order can have several split waybills (multiple parcels). | shippings[].shippingCodeOrder detail( orders) | Available only when the order is split into multiple parcels; listed in the order BVSHOP returns them. |
order.orderSource | Order source Order source as returned by BVSHOP: 0 = online store, 1 = created in admin, 2 = POS store, 3 = created via API. | orderSourceOrder detail( orders) | Available as soon as the order is fetched into Vanta. |
order.inventoryPosStoreId | Stock-deducting store ID ID of the store whose stock this order actually deducted; empty when online stock is used. | inventoryPosStoreIdOrder detail( orders) | Available only when the order deducts a store's stock; empty when online stock is used. |
9. FreeStore
FreeStore fields fall into four categories: Order amounts, Payment, Tax & invoice and Reconciliation keys. All of them come from the order detail the system already fetches; no other API is called. FreeStore has no Seller settlement data, and costs exist only in FreeStore's product data, not on orders, so Cost is not shown either. The summary cards at the top show the order total, payment method and payment status.
- After creation, updated only when FreeStore reports a status change: once the system creates an order from a pending, awaiting-shipment FreeStore order, it switches the FreeStore order to processing, so polling no longer fetches it; when FreeStore sends an order status change notification, the system reads the order again and refreshes the details.
- Subtotal lines are listed one by one: "Subtotal lines" shows one row per line under the field name, with FreeStore's line name on the left (e.g. 商品小計, 優惠券(A1234), 折抵運費(促銷活動)) and the amount on the right, in FreeStore's order; the same kind of line can appear more than once (e.g. shipping and a shipping discount) and every line is listed.
- Payment time is read as Taiwan time: FreeStore times carry no time zone, so the system treats them as Taiwan time; the empty value FreeStore returns before payment (0000-00-00) is shown as blank.
- Shipping fee: "Shipping fee" is also written to the order's shipping fee.
- Payment methods keep the platform values: "Payment method code" is FreeStore's payment method code and "Payment method" is FreeStore's payment method description; both are shown exactly as FreeStore returns them.
- Tax ID and invoice title go to the order's invoice information: when the buyer asks for a business (triplicate) invoice, FreeStore's tax ID and invoice title fill in the order's buyer tax ID and name (existing values are not overwritten) and are not shown on this tab.
Order amounts
Available as soon as the order is fetched into Vanta and updated by later order syncs.
| Field | Name | FreeStore field | When available |
|---|---|---|---|
order.order_subtotals | Subtotal lines Each order subtotal line, as its name (name of the order_subtotals entry, FreeStore's display name, e.g. 商品小計, 優惠券(A1234), 折抵運費(促銷活動)) and amount (value of the order_subtotals entry), in FreeStore's order without de-duplication. The line types (code) listed in the docs are sub_total, shipping, reward, coupon, site_discount and promotion; other types in the response (e.g. cod, total) are kept as well. | order_subtotals[].value(label: order_subtotals[].name)Order details( orders) | Available as soon as the order is fetched into Vanta. |
order.shipping_fee | Shipping fee Shipping fee (FreeStore docs - 運費); also written to the order's shipping fee. | shipping_feeOrder details( orders) | Available as soon as the order is fetched into Vanta. |
order.total | Order total Order total (FreeStore docs - 訂單總金額). | totalOrder details( orders) | Available as soon as the order is fetched into Vanta. |
Payment
Available as soon as the order is fetched into Vanta; the payment time appears once the buyer pays.
| Field | Name | FreeStore field | When available |
|---|---|---|---|
order.payment_code | Payment method code Payment method code as returned by FreeStore (e.g. allpay_credit, allpay_c2c, cod). | payment_codeOrder details( orders) | Available as soon as the order is fetched into Vanta. |
order.payment_method | Payment method Payment method description as returned by FreeStore (FreeStore docs - 付款方式說明). | payment_methodOrder details( orders) | Available as soon as the order is fetched into Vanta. |
order.payment_status | Payment status Payment status as returned by FreeStore (PAID = paid, UNPAID = not yet paid). | payment_statusOrder details( orders) | Available as soon as the order is fetched into Vanta. |
order.payment_time | Payment time Payment time (FreeStore docs - 付款時間); FreeStore times carry no time zone and are read as Taiwan time. | payment_timeOrder details( orders) | Available after the buyer pays; empty for cash-on-delivery orders before shipment. |
order.currency_code | Currency Order currency (FreeStore docs - 幣別; e.g. TWD). | currency_codeOrder details( orders) | Available as soon as the order is fetched into Vanta. |
Tax & invoice
The invoice number appears after FreeStore issues the invoice; the carrier and donation code appear only when the buyer entered them at checkout. The tax ID and invoice title are written to the order's invoice information instead.
| Field | Name | FreeStore field | When available |
|---|---|---|---|
order.invoice_number | Invoice number Invoice number (FreeStore docs - 發票號碼). | invoice_numberOrder details( orders) | Available after FreeStore issues the invoice. |
order.invoice_carrier_num | Invoice carrier Invoice carrier number (FreeStore docs - 載具編號). | invoice_carrier_numOrder details( orders) | Available only when the buyer entered a carrier at checkout. |
order.invoice_lovecode | Donation code Donation code (FreeStore docs - 捐贈愛心碼). | invoice_lovecodeOrder details( orders) | Available only when the buyer chose to donate the invoice at checkout. |
Reconciliation keys
Available as soon as the order is fetched into Vanta; the tracking number appears after it is sent back on shipment, and UTM values only on orders referred through tagged links.
| Field | Name | FreeStore field | When available |
|---|---|---|---|
order.order_id | FreeStore order number FreeStore order number (FreeStore docs - 訂單編號, 10 digits); the same as the Vanta order number. | order_idOrder details( orders) | Available as soon as the order is fetched into Vanta. |
order.bb_id | Buy Button ID Buy Button ID as returned by FreeStore (FreeStore docs - Buy Button 專屬編號). | bb_idOrder details( orders) | Available as soon as the order is fetched into Vanta. |
order.tracking_number | Tracking number Parcel tracking number (FreeStore docs - 包裹追蹤碼). | tracking_numberOrder details( orders) | Available after the tracking number is sent back to FreeStore on shipment. |
order.utm_source | UTM source The utm_source of the referring link (FreeStore docs - orders referred through ?utm_source=OOOOO). | utm_sourceOrder details( orders) | Available only on orders referred through links with UTM parameters. |
order.utm_medium | UTM medium The utm_medium of the referring link. | utm_mediumOrder details( orders) | Available only on orders referred through links with UTM parameters. |
order.utm_campaign | UTM campaign The utm_campaign of the referring link. | utm_campaignOrder details( orders) | Available only on orders referred through links with UTM parameters. |
10. Cyberbiz
Cyberbiz has fields in five categories: Order amounts, Payment, Tax & invoice, Reconciliation keys and Cost; Cyberbiz has no Seller settlement fields. All of them come from the same Cyberbiz order API used to fetch orders (GET /v1/orders); the summary cards at the top are "Order total", "Payment type" and "Payment status".
- Amounts are in New Taiwan dollars: Cyberbiz orders have no currency field, so amounts are stored as TWD.
- Updated with each order fetch: the system only imports Cyberbiz orders that are open, paid or cash on delivery, and unshipped, and updates the details each time it fetches them. Once an order is shipped or cancelled in Cyberbiz it is no longer updated, so invoices and tracking numbers created afterwards are not added.
- Shipping: "Shipping fee" is written to the order's shipping fee when the order is created; for orders imported before this feature, it is filled in the first time the details are fetched. Only an empty shipping fee is filled; an existing value is never overwritten.
- Invoice tax ID and title go on the order: the tax ID and title of a Cyberbiz invoice are not listed here; they are written to the order's invoice information (buyer tax ID and name), filling only empty fields and never overwriting values already entered. When both are present, the buyer type is set to business.
- Fields with several values: coupon, multiple payment, line item and fulfillment fields can hold several values per order, listed in Cyberbiz's order. "Coupon discounts", "Split payments" and "Item costs" list one row per entry under the field name, with the coupon name, payment name or item SKU (the item title when it has no SKU) on the left and the amount on the right, showing - where a value is missing; other multi-value fields follow the same order and show - where a position has no value.
- Undocumented fields are stored as returned: Cyberbiz does not document the meaning of "Third-party discount" or "POS information", nor whether "Item costs" is a unit cost or a line total; they are stored as the platform returns them, without further calculation.
- Personal data: "Mobile barcode carrier" and "Invoice donation code" are cleared when the order is de-identified.
Order amounts
| Field | Name | Cyberbiz field | When available |
|---|---|---|---|
| Item amounts | |||
prices.total_line_items_price | Line items total Total price of the line items. | prices.total_line_items_priceOrder prices( orders) | Available as soon as the order is fetched into Vanta. |
| Discounts and credits | |||
prices.special_collection_discount | Campaign discount Marketing campaign discount. | prices.discounts.special_collection_discountOrder prices( orders) | Available as soon as the order is fetched into Vanta. |
prices.vip_discount | VIP discount VIP discount. | prices.discounts.vip_discountOrder prices( orders) | Available as soon as the order is fetched into Vanta. |
prices.shop_discount_name | Store-wide promotion Store-wide promotion name. | prices.discounts.shop_discount.nameOrder prices( orders) | Available only when a store-wide promotion applies to the order. |
prices.shop_discount_amount | Store-wide promotion discount Store-wide promotion discount. | prices.discounts.shop_discount.amountOrder prices( orders) | Available only when a store-wide promotion applies to the order. |
prices.coupon_discounts_code | Coupon codes Code of each coupon, in the order of the coupon details and matching the coupon discounts one by one; coupons without a code are null. | prices.discounts.coupon_discounts[].codeOrder prices( orders) | Available only when the buyer used coupons; an order can have several. |
prices.coupon_discounts_amount | Coupon discounts Discount of each coupon, as its name (name of the coupon_discounts entry) and amount (amount of the coupon_discounts entry), in the order of the coupon details. | prices.discounts.coupon_discounts[].amount(label: prices.discounts.coupon_discounts[].name)Order prices( orders) | Available only when the buyer used coupons; an order can have several. |
prices.bonus_consumed | Bonus points discount Bonus points discount. | prices.discounts.bonus_consumedOrder prices( orders) | Available as soon as the order is fetched into Vanta. |
prices.price_discount | Store manager discount Store manager discount. | prices.discounts.price_discountOrder prices( orders) | Available as soon as the order is fetched into Vanta. |
prices.third_party_discount | Third-party discount Cyberbiz documents this only as "third party discount", without saying where the discount comes from or who bears it; stored as returned. | prices.discounts.third_party_discountOrder prices( orders) | Available as soon as the order is fetched into Vanta. |
| Shipping | |||
prices.shipping_rate_price | Shipping fee Shipping fee. The order's shipping fee is also taken from this value. | prices.shipping_rate_priceOrder prices( orders) | Available as soon as the order is fetched into Vanta. |
prices.total_price | Order total Total price of the order. | prices.total_priceOrder prices( orders) | Available as soon as the order is fetched into Vanta. |
Payment
| Field | Name | Cyberbiz field | When available |
|---|---|---|---|
payment.payment_name | Payment type Payment type, as returned by Cyberbiz. | payment_nameOrder payment( orders) | Available as soon as the order is fetched into Vanta. |
payment.payment_method | Payment method name Payment method name, as returned by Cyberbiz. | payment_methodOrder payment( orders) | Available as soon as the order is fetched into Vanta. |
payment.multiple_payment_infos_amount | Split payments Each payment when several payment methods were used, as its name (name of the multiple_payment_infos entry) and amount (amount of the multiple_payment_infos entry), in the order of the payment details. | multiple_payment_infos[].amount(label: multiple_payment_infos[].name)Order payment( orders) | Available only when the order was paid with several payment methods. |
payment.financial_status | Payment status Raw payment status (e.g. paid, cod). | statuses.financial_statusOrder payment( orders) | Available as soon as the order is fetched into Vanta. |
Tax & invoice
| Field | Name | Cyberbiz field | When available |
|---|---|---|---|
order.invoice_no | E-invoice number E-invoice number. | einvoice.invoice_noOrder( orders) | Available after Cyberbiz issues the invoice. |
order.invoice_status | Invoice status Invoice status, as returned by Cyberbiz. | einvoice.invoice_statusOrder( orders) | Available after Cyberbiz issues the invoice. |
order.paper_invoice_no | Paper invoice number Paper invoice number. | paper_invoice_noOrder( orders) | Available only when a paper invoice is issued. |
order.phone_barcode | Mobile barcode carrier Mobile barcode carrier number. Cleared when the order is de-identified. | einvoice.phone_barcodeOrder( orders) | Available only when the buyer stores the invoice in a mobile barcode carrier. |
order.love_code | Invoice donation code Invoice donation code. Cleared when the order is de-identified. | einvoice.love_codeOrder( orders) | Available only when the buyer donates the invoice. |
order.line_items_tax_type_id | Item tax types Tax type of each line item (inclusive_tax - taxable; zero_tax - zero-rated; exclusive_tax - tax-exempt), in line item order; line items without a value are null. | line_items[].tax_type_idOrder( orders) | Available as soon as the order is fetched into Vanta. |
Reconciliation keys
| Field | Name | Cyberbiz field | When available |
|---|---|---|---|
order.id | Cyberbiz order ID Cyberbiz order ID, as used by the Cyberbiz API. | idOrder( orders) | Available as soon as the order is fetched into Vanta. |
order.order_number | Cyberbiz order number Cyberbiz order number. | order_numberOrder( orders) | Available as soon as the order is fetched into Vanta. |
order.tracking_number | Tracking numbers Tracking number of each fulfillment, in fulfillment order. | fulfillments[].tracking_numberOrder( orders) | Available after Cyberbiz creates fulfillments; an order can have several. |
order.transaction_number | Third-party transaction number Third-party transaction number. | transaction_numberOrder( orders) | Available as soon as the order is fetched into Vanta. |
order.merchant_trade_no | Third-party integration number Third-party integration number. | merchant_trade_noOrder( orders) | Available as soon as the order is fetched into Vanta. |
order.from_device | Order source Order source, as returned by Cyberbiz. | from_deviceOrder( orders) | Available as soon as the order is fetched into Vanta. |
order.pos_shop_id | POS shop ID ID of the shop the POS salesperson belongs to. | pos_info.pos_shop_idOrder( orders) | Available only for POS orders. |
order.pos_id | POS terminal ID ID of the POS terminal used for the sale. | pos_info.pos_idOrder( orders) | Available only for POS orders. |
order.pos_name | POS terminal name Name of the POS terminal used for the sale. | pos_info.pos_nameOrder( orders) | Available only for POS orders. |
order.pos_info | POS information Cyberbiz documents this only as "POS-related information", without describing its content; stored as returned. | pos_info.pos_infoOrder( orders) | Available only for POS orders. |
order.branch_store_no | Pickup store number Pickup store number. | branch_store.store_noOrder( orders) | Available only when the buyer chose in-store pickup. |
order.branch_store_name | Pickup store name Pickup store name. | branch_store.nameOrder( orders) | Available only when the buyer chose in-store pickup. |
Cost
Available only when the merchant has set product costs in Cyberbiz.
| Field | Name | Cyberbiz field | When available |
|---|---|---|---|
order.line_items_cost | Item costs Cost of each line item, as the item's SKU (the item title when it has no SKU) and cost (cost of the line_items entry), in line item order. Cyberbiz does not document whether it is a unit cost or a line total; stored as returned. | line_items[].cost(label: line_items[].sku)Order( orders) | See category note |
11. EasyStore
EasyStore fields fall into five categories: Order amounts, Seller settlement, Payment, Tax & invoice and Reconciliation keys. All of them come from the order detail the system already fetches; no other API is called. EasyStore has no cost fields. The summary cards at the top show the order total, payment status and total transaction fee.
- Updated only while the order is ready to ship: the system only fetches EasyStore orders that are paid or cash on delivery and not yet shipped, and refreshes the details each time; changes on EasyStore after the order ships or is cancelled are not written back.
- Seller settlement only has the total transaction fee: "Total transaction fee" is stored as EasyStore returns it; the EasyStore documentation does not say whether the buyer or the seller bears it.
- Transactions, tax lines and discount codes list one row per entry: "Transactions", "Tax lines" and "Discount codes" show each name with its amount in EasyStore's order; failed transactions are listed too, so check "Transaction statuses".
- Shipping fee: "Shipping fee" and the order's own shipping fee come from the same EasyStore field.
- Invoices: EasyStore has no invoice fields; Tax & invoice only has the tax-included flag, tax total and tax lines.
Order amounts
Available as soon as the order is fetched into Vanta and updated by later order syncs.
| Field | Name | EasyStore field | When available |
|---|---|---|---|
order.total_line_item_price | Line item total The total price of all line items in the order; in recorded EasyStore responses this is the list-price total before line item discounts. | total_line_item_priceOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.subtotal_price | Subtotal Documented by EasyStore as "The total price of all items before discounts and taxes", but in recorded EasyStore responses it already has line item discounts deducted (the sum of each line item's discounted amount), unlike the line item total. | subtotal_priceOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
| Discounts and deductions | |||
order.total_discount | Total discount The total amount of discounts applied to the order. | total_discountOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.discount_codes | Discount codes Each discount code applied to the order with its amount (The list of discount codes applied to the order), in EasyStore's order. | discount_codes[].amount(label: discount_codes[].code)Order detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.total_credit_used | Store credit used The total amount of credit used for the order. | total_credit_usedOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
| Shipping | |||
order.total_shipping_fee | Shipping fee The total shipping fee for the order; the order's shipping fee is also taken from this field. | total_shipping_feeOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.total_price | Order total The final total price of the order. | total_priceOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
Seller settlement
Available as soon as the order is fetched into Vanta. EasyStore only provides the total transaction fee; it has no platform fee or payout data.
| Field | Name | EasyStore field | When available |
|---|---|---|---|
order.total_transaction_fee | Total transaction fee The total transaction fee for the order; the documentation does not say whether the buyer or the seller bears it. | total_transaction_feeOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
Payment
Available as soon as the order is fetched into Vanta; transactions reflect the last fetch.
| Field | Name | EasyStore field | When available |
|---|---|---|---|
order.financial_status | Payment status The financial status of the order as returned by EasyStore (e.g. paid, unpaid, partially_paid). | financial_statusOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.currency_code | Currency The currency code in which the order was placed. | currency_codeOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.cod_type | COD type The cash on delivery type for the order as returned by EasyStore (0 means not a COD order, 1 means a COD order; other values are not documented). | cod_typeOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.transactions_amount | Transactions Payment gateway (as returned by EasyStore, e.g. cod, linepay, bank-transfer) and amount of each transaction, in EasyStore's transaction order; failed transactions are listed too, so check the transaction status. | transactions[].amount(label: transactions[].gateway)Order detail( orders.json) | Reflects transactions as of the last fetch, in EasyStore's transaction order; failed transactions are listed too. |
order.transactions_status | Transaction statuses Status of each transaction as returned by EasyStore (e.g. pending, success, failed); the documentation does not list every possible value. | transactions[].statusOrder detail( orders.json) | Reflects transactions as of the last fetch, in EasyStore's transaction order. |
Tax & invoice
Available as soon as the order is fetched into Vanta. EasyStore has no invoice fields.
| Field | Name | EasyStore field | When available |
|---|---|---|---|
order.taxes_included | Taxes included Indicates if taxes are included in the line items price. | taxes_includedOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.total_tax | Total tax The total tax amount for the order. | total_taxOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.tax_line_price | Tax lines Name (e.g. GST) and tax amount of each tax line (The tax line details for the order), in EasyStore's order. | tax_line[].price(label: tax_line[].name)Order detail( orders.json) | Available only when the order has tax lines. |
order.tax_line_rate | Tax rates Rate of each tax line as returned by EasyStore, in EasyStore's order; the documentation does not state its unit. | tax_line[].rateOrder detail( orders.json) | Available only when the order has tax lines. |
Reconciliation keys
Available as soon as the order is fetched into Vanta; fulfillments appear once a fulfillment is created in EasyStore.
| Field | Name | EasyStore field | When available |
|---|---|---|---|
order.id | EasyStore order ID The unique identifier for the order; different from the order number. | idOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.order_number | EasyStore order number The order number displayed to the customer. | order_numberOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.source_type | Order source The source where the order was created, as returned by EasyStore (e.g. online_store, admin_panel). | source_typeOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.transactions_id | Transaction IDs EasyStore identifier of each transaction, in EasyStore's transaction order. | transactions[].idOrder detail( orders.json) | Available as soon as the order is fetched into Vanta. |
order.fulfillments_id | Fulfillment IDs EasyStore identifier of each fulfillment associated with the order, in EasyStore's order. | fulfillments[].idOrder detail( orders.json) | Available once a fulfillment is created in EasyStore. |
order.fulfillments_tracking_number | Tracking numbers Tracking number of each fulfillment, in EasyStore's order. | fulfillments[].tracking_numberOrder detail( orders.json) | Available once a fulfillment with a tracking number is created in EasyStore. |
order.fulfillments_tracking_company | Carriers Tracking company of each fulfillment, in EasyStore's order. | fulfillments[].tracking_companyOrder detail( orders.json) | Available once a fulfillment with a tracking company is created in EasyStore. |
12. 1shop
1shop fields fall into four categories: Order amounts, Payment, Tax & invoice and Reconciliation keys. All of them come from the order detail the system already fetches; no other API is called. 1shop has no Seller settlement or Cost fields. The summary cards at the top show the total amount, payment method and payment status.
- Updated only while the order is unshipped on 1shop: the system only fetches 1shop orders that are pending or confirmed, paid or cash on delivery, and not yet shipped, and refreshes the details each time; changes after the order ships or is cancelled on 1shop are not written back, so cash-on-delivery payment dates, invoices issued after shipment and refunds never appear.
- "Payment fee" is under Order amounts: 1shop docs list it with the cart amounts and do not say whether the buyer pays it or it is deducted from the seller's proceeds, so it follows the docs and is not listed under Seller settlement.
- Status fields show 1shop's raw values: "Payment method", "Payment status" and "Tax type" are 1shop codes; see the table below for what each value means.
- An order can have several invoices: invoice fields hold one value per invoice in the order 1shop returns them; the same position is the same invoice.
- Shipping fee: the order's shipping fee is already written from 1shop's shipping fee when the order is created and on every re-sync; "Shipping fee" here is the same raw value.
- Company invoice tax ID and title go to the order's invoice details: when a 1shop invoice record has a tax ID and invoice title, the system takes the first invoice that has both and writes them to the order's buyer tax ID and name (only fields that are still empty; values the warehouse already entered are kept; the buyer type is set to company when both are present); they are not listed as separate fields on this tab.
- The invoice carrier is personal data: "Invoice carrier" is cleared when the order is de-identified.
Order amounts
Available as soon as the order is fetched into Vanta and updated by later order syncs.
| Field | Name | 1shop field | When available |
|---|---|---|---|
order.sub_total | Cart subtotal Cart subtotal, including every single product, bundle and charge item. | cart.sub_totalOrder detail( {order_number}) | Available as soon as the order is fetched into Vanta. |
order.payment_fee | Payment fee Payment fee; 1shop docs list it with the cart amounts and do not say whether the buyer pays it or it is deducted from the seller's proceeds. | cart.payment_feeOrder detail( {order_number}) | Available as soon as the order is fetched into Vanta. |
| Shipping | |||
order.logistic_fee | Shipping fee Shipping fee. | cart.logistic_feeOrder detail( {order_number}) | Available as soon as the order is fetched into Vanta. |
| Refunds | |||
order.refund | Refund amount Refund amount. | cart.refundOrder detail( {order_number}) | Has an amount only after a refund; the system only fetches unshipped 1shop orders, so refunds after shipment never arrive. |
order.total_price | Total amount Total amount (1shop docs do not explain how it is calculated). | cart.total_priceOrder detail( {order_number}) | Available as soon as the order is fetched into Vanta. |
Payment
Available as soon as the order is fetched into Vanta; the payment date appears once the order is paid.
| Field | Name | 1shop field | When available |
|---|---|---|---|
order.payment | Payment method Payment method as returned by 1shop: atm = ATM transfer, cod = cash on delivery, credit = credit card, credit3/credit6/credit12/credit24 = credit card in 3/6/12/24 installments, regular = recurring payment, paypal = PayPal, code = convenience store payment code, vacc = virtual account, c2c = pay at convenience store pickup, linepay = LINE Pay, icash = icash Pay, applepay = Apple Pay, nocard3/nocard6/nocard12/nocard24 = cardless installments in 3/6/12/24 periods, nopay = no payment required. | order.paymentOrder detail( {order_number}) | Available as soon as the order is fetched into Vanta. |
order.payment_status | Payment status Payment status as returned by 1shop: pending = awaiting payment, need_confirm = payment to be confirmed, paid = paid, cod = cash on delivery, refunded = refunded. | order.payment_statusOrder detail( {order_number}) | Available as soon as the order is fetched into Vanta. |
order.payment_date | Payment date Payment date, stored as the raw 1shop string (e.g. 2022-04-19 18:47:35); 1shop docs do not state its time zone. | order.payment_dateOrder detail( {order_number}) | Available only after the order is paid; the system only fetches unshipped 1shop orders, so COD orders paid on delivery never get a value. |
Tax & invoice
Available once 1shop creates the invoice record; the invoice number appears once the invoice is issued.
| Field | Name | 1shop field | When available |
|---|---|---|---|
order.receipt_tax_type | Tax type Tax type as returned by 1shop: 1 = taxable, 2 = zero-rated, 3 = tax-exempt, 4 = mixed taxable and tax-exempt; one value per invoice, in the order 1shop returns them. | receipt[].tax_typeOrder detail( {order_number}) | Available as soon as the order is fetched into Vanta. |
order.receipt_carruer_num | Invoice carrier Mobile barcode or citizen digital certificate (personal invoices only); one value per invoice, in the order 1shop returns them. The 1shop field name is spelled carruer_num. | receipt[].carruer_numOrder detail( {order_number}) | Available as soon as the order is fetched into Vanta. |
order.receipt_invoice_number | Invoice number Invoice number; one value per invoice, in the order 1shop returns them. | receipt[].invoice_numberOrder detail( {order_number}) | Available only after the invoice is issued; the system only fetches unshipped 1shop orders, so invoices issued after shipment never arrive. |
Reconciliation keys
Available as soon as the order is fetched into Vanta; the third-party payment number appears once the order is paid.
| Field | Name | 1shop field | When available |
|---|---|---|---|
order.order_number | 1shop order number Order number (the order number in Vanta). | order.order_numberOrder detail( {order_number}) | Available as soon as the order is fetched into Vanta. |
order.payment_third_party_no | Third-party payment number Third-party number of the successful payment, e.g. the ECPay number. | order.payment_third_party_noOrder detail( {order_number}) | Available only after the payment succeeds. |
13. Coupang
Coupang has fields in four categories: Order amounts, Payment, Tax & invoice and Reconciliation keys; Coupang Taiwan has no Seller settlement or Cost fields (the seller settlement API is not available in Taiwan; see the reports in the Coupang Wing seller center for commissions and payouts). All of them come from the same Coupang order API used to fetch orders (ordersheets); the summary cards at the top are "Paid at", "Cash on delivery" and "Invoice type".
- No order total: Coupang has no order-level total, so Order amounts is listed per item and per shipment box, and the system does not add it up.
- Updated with order fetching: polling only picks up Coupang orders in the "payment completed" status and refreshes the data each time; once the order is accepted on Coupang and moves into shipping, polling no longer picks it up, so waybill numbers uploaded later are not filled in by polling. Orders split into several shipment boxes are accepted box by box; when a round only picks up some of the boxes, the details keep the content from the last round that had all of them.
- Items and shipment boxes: a Coupang order can be split into several shipment boxes. Each item amount row shows the item's option ID (vendorItemId) on the left and lists the items as Coupang returns them (cancelled items included); "Shipping fee", "Remote area shipping fee" and "COD shipping fee" show the shipment box ID on the left; "Shipment box ID" and "Waybill number" are listed in box order, with - where a box has no value.
- Shipping fee: the order's own shipping fee still comes from the first box as before; this page only lists the raw value of each box and does not change the order.
- Invoice information is stored as returned: the Tax & invoice fields come from the order's extra properties (extraProperties) and are stored as returned; Coupang does not document how the two invoiced amounts relate to the item amounts, so nothing is derived from them.
- Personal data: "Invoice applied value" is cleared when the order is de-identified.
Order amounts
Available as soon as the order is fetched into Vanta. Coupang has no order-level total, so amounts are listed per item and per shipment box.
| Field | Name | Coupang field | When available |
|---|---|---|---|
| Item amounts | |||
order.orderItems_salesPrice | Item unit price Price of one unit of each item, as the item's option ID (vendorItemId) and the unit price, in shipment box and item order. | orderItems[].salesPrice(label: orderItems[].vendorItemId)Order detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
order.orderItems_orderPrice | Item payment amount Payment price of each item (Coupang docs - salesPrice × shippingCount), as the item's option ID (vendorItemId) and the amount, in shipment box and item order. | orderItems[].orderPrice(label: orderItems[].vendorItemId)Order detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
| Discounts and credits | |||
order.orderItems_discountPrice | Item total discount Total discount of each item (Coupang docs - instantCouponDiscount + downloadableCouponDiscount + coupangDiscount), as the item's option ID (vendorItemId) and the amount. | orderItems[].discountPrice(label: orderItems[].vendorItemId)Order detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
order.orderItems_instantCouponDiscount | Instant discount coupon Instant discount coupon amount of each item, as the item's option ID (vendorItemId) and the amount. | orderItems[].instantCouponDiscount(label: orderItems[].vendorItemId)Order detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
order.orderItems_downloadableCouponDiscount | Downloadable coupon Downloadable coupon discount of each item, as the item's option ID (vendorItemId) and the amount. | orderItems[].downloadableCouponDiscount(label: orderItems[].vendorItemId)Order detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
order.orderItems_coupangDiscount | Coupang-supported discount Discount supported by Coupang (cart or category coupons, etc.) of each item, as the item's option ID (vendorItemId) and the amount. | orderItems[].coupangDiscount(label: orderItems[].vendorItemId)Order detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
| Shipping | |||
order.shippingPrice | Shipping fee Shipping fee of each shipment box, as the shipment box ID (shipmentBoxId) and the amount. The order's shipping fee is taken from the first box. | shippingPrice(label: shipmentBoxId)Order detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
order.remotePrice | Remote area shipping fee Remote area (mountain and island) shipping fee of each shipment box, as the shipment box ID (shipmentBoxId) and the amount. | remotePrice(label: shipmentBoxId)Order detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
order.codDeliveryFee | COD shipping fee Cash on delivery (COD) shipping fee of each shipment box, as the shipment box ID (shipmentBoxId) and the amount. | codDeliveryFee(label: shipmentBoxId)Order detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
Payment
| Field | Name | Coupang field | When available |
|---|---|---|---|
order.paidAt | Paid at Time of payment. | paidAtOrder detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
order.isCod | Cash on delivery Whether the order is cash on delivery (COD). | isCodOrder detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
order.currencyCode | Currency Currency code (ISO-4217, three uppercase letters). Coupang carries a currency on every amount object; this is the currency of the first box's shipping fee. | shippingPrice.currencyCodeOrder detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
Tax & invoice
Available as soon as the order is fetched into Vanta; Coupang returns invoice information only in markets that support invoices.
| Field | Name | Coupang field | When available |
|---|---|---|---|
order.taxReceiptInfo_receiptOption | Receipt option Receipt option, as returned by Coupang (PAPER, E-GUI). | extraProperties.taxReceiptInfo.receiptOptionOrder detail( ordersheets) | Available only when Coupang returns invoice information (extraProperties.taxReceiptInfo). |
order.taxReceiptInfo_appliedType | Invoice type Applied invoice type, as returned by Coupang (PERSONAL_COUPANG_MEMBER_CARRIER, PERSONAL_MOBILE_BARCODE_CARRIER, DONATION, BUSINESS). | extraProperties.taxReceiptInfo.appliedTypeOrder detail( ordersheets) | Available only when Coupang returns invoice information (extraProperties.taxReceiptInfo). |
order.taxReceiptInfo_appliedValue | Invoice applied value Applied value of the invoice (Coupang docs - integrated receipt number or information), stored as returned. Cleared when the order is de-identified. | extraProperties.taxReceiptInfo.appliedValueOrder detail( ordersheets) | Available only when Coupang returns invoice information with a value for the applied type. |
order.invoiceAmountInfo_invoiceAmountToBuyer | Amount invoiced to buyer Amount invoiced to the buyer. Coupang does not document how it relates to the item amounts; stored as returned. | extraProperties.invoiceAmountInfo.invoiceAmountToBuyerOrder detail( ordersheets) | Available only when Coupang returns invoice amount information (extraProperties.invoiceAmountInfo). |
order.invoiceAmountInfo_invoiceAmountToCoupang | Amount invoiced to Coupang Amount invoiced to Coupang. Coupang does not document how it relates to the item amounts; stored as returned. | extraProperties.invoiceAmountInfo.invoiceAmountToCoupangOrder detail( ordersheets) | Available only when Coupang returns invoice amount information (extraProperties.invoiceAmountInfo). |
order.invoiceAmountInfo_currency | Invoice amount currency Currency code of the invoice amounts. | extraProperties.invoiceAmountInfo.currencyOrder detail( ordersheets) | Available only when Coupang returns invoice amount information (extraProperties.invoiceAmountInfo). |
Reconciliation keys
| Field | Name | Coupang field | When available |
|---|---|---|---|
order.orderId | Coupang order ID Coupang order number, which is also the Vanta order number. | orderIdOrder detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
order.shipmentBoxId | Shipment box ID Shipment number (shipmentBoxId) of each shipment box, in box order; it is the platform fulfillment number of the fulfillment. | shipmentBoxIdOrder detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
order.invoiceNumber | Waybill number Waybill number of each shipment box, in box order; boxes without one are null. | invoiceNumberOrder detail( ordersheets) | Available after the shipment box's waybill number is uploaded. |
order.refer | Payment channel Where the payment was made, as returned by Coupang (e.g. 아이폰앱 iPhone app, 안드로이드앱 Android app, PC웹 PC web). | referOrder detail( ordersheets) | Available as soon as the order is fetched into Vanta. |
14. Ruten
Ruten fields fall into four categories: Order amounts, Seller settlement, Payment and Reconciliation keys. All of them come from the order detail the system already fetches; no other API is called. The Ruten order detail has no invoice data and no cost fields, so Tax & invoice and Cost are not shown. The summary cards at the top show the checkout total, seller income and payment status.
- Updated only while the order is to be confirmed or ready to ship: each order sync re-reads Ruten orders created in the last 7 days that are to be confirmed or ready to ship and updates them; changes on Ruten after the order ships or is cancelled are not written back.
- One row per item for item prices: "Original price" and "Campaign price" list one row per item under the field name, with the item and spec name on the left and the unit price (not multiplied by the quantity) on the right, in Ruten's order.
- Seller income as returned by Ruten: "Seller income" is the seller income Ruten returns; the Ruten documentation does not say whether fees have been deducted and has no fee fields.
- Shipping fee: "Shipping fee paid by buyer" and the order's own shipping fee come from the same Ruten field.
- Payment method and status as returned by Ruten: "Payment method code" and "Payment status" show Ruten's codes as is (e.g. PP_CRD, Paid, Transfer).
Order amounts
Available as soon as the order is fetched into Vanta and updated by later order syncs.
| Field | Name | Ruten field | When available |
|---|---|---|---|
| Item amounts | |||
order.item_list_original_price | Original price Original price of each item, labeled with the item and spec name, in Ruten's order; it is a unit price, see the order items for quantities. | item_list[].original_price(label: item_list[].item_name)Order detail( detail) | Available as soon as the order is fetched into Vanta. |
order.item_list_discount_price | Campaign price Campaign price of each item (per the Ruten documentation, the discounted price when the item joins a campaign, otherwise the same as the original price), labeled with the item and spec name, in Ruten's order; it is a unit price. | item_list[].discount_price(label: item_list[].item_name)Order detail( detail) | Available as soon as the order is fetched into Vanta. |
order.item_amount | Item subtotal Subtotal of the order's item amounts. | checkout_info.item_amountOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
| Discounts and credits | |||
order.coupon_from_ruten | Ruten discount code Amount deducted by Ruten discount codes; 0 means none was used. | checkout_info.coupon_from_rutenOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
order.coupon_from_seller | Seller discount code Amount deducted by the seller's discount codes; 0 means none was used. | checkout_info.coupon_from_sellerOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
order.rpoint | Ruten points Amount deducted by Ruten points. | checkout_info.rpointOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
| Shipping | |||
order.original_shipping_fee | Original shipping fee Original shipping fee. | checkout_info.original_shipping_feeOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
order.buyer_paid_shipping_fee | Shipping fee paid by buyer Shipping fee actually paid by the buyer; the order's shipping fee is also taken from this field. | checkout_info.buyer_paid_shipping_feeOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
order.total_amount | Checkout total Checkout total (per the Ruten documentation, the edited amount when the buyer edited the order amount; otherwise item subtotal − Ruten/seller discount codes + shipping fee paid by the buyer − Ruten points). | checkout_info.total_amountOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
Seller settlement
Available as soon as the order is fetched into Vanta; the transfer time appears once Ruten transfers the payout. The Ruten documentation has no fee or commission fields.
| Field | Name | Ruten field | When available |
|---|---|---|---|
order.order_income | Seller income Amount received by the seller; the documentation does not say whether fees have been deducted. | checkout_info.order_incomeOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
order.transfer_time | Transfer time Payout transfer time (per the Ruten documentation, the transfer time for Ruten-supported payments; empty for the seller's own payment flow). | payment_info.transfer_timeOrder detail( detail) | Available once Ruten transfers the payout; always empty for orders paid through the seller's own payment flow. |
Payment
Available as soon as the order is fetched into Vanta; the payment time appears once the buyer pays.
| Field | Name | Ruten field | When available |
|---|---|---|---|
order.pay_way | Payment method code Payment method code as returned by Ruten (see the "payment method" appendix of the Ruten documentation; e.g. PP_CRD, FAMI_COD). | payment_info.pay_wayOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
order.pay_status | Payment status Payment status as returned by Ruten (Ruten-supported payments: Unpaid, Paid, Transfer = transferred to the seller, Delay = transfer delayed, Pause = transfer paused, PauseRefund = paused and refunded to the buyer; seller's own payment flow: PaymentUnnotified, PaymentNotified). | payment_info.pay_statusOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
order.pay_time | Payment time Payment time (per the Ruten documentation, the successful payment time for Ruten-supported payments; empty for the seller's own payment flow). | payment_info.pay_timeOrder detail( detail) | Available once the buyer pays; always empty for orders paid through the seller's own payment flow. |
Reconciliation keys
Available as soon as the order is fetched into Vanta; tracking numbers appear after shipment, and the pickup store only for convenience store or i-Mailbox pickup orders.
| Field | Name | Ruten field | When available |
|---|---|---|---|
order.order_id | Ruten order number Ruten order number; also used as the Vanta order number. | order_info.order_idOrder detail( detail) | Available as soon as the order is fetched into Vanta. |
order.package_info_tracking_number | Tracking number Shipment number / tracking number of each package, in Ruten's order. | shipping_info.package_info[].tracking_numberOrder detail( detail) | Available after shipment. |
order.receiver_store_name | Pickup store Name of the recipient's pickup convenience store or i-Mailbox. | shipping_info.receiver_info.receiver_store_nameOrder detail( detail) | Available only for convenience store or i-Mailbox pickup orders. |
15. Yahoo SCM
Yahoo SCM fields fall into three categories: Order amounts, Reconciliation keys and Cost, all taken from the ready-to-ship order query the order fetch already calls, with no extra API call; Yahoo SCM has no seller settlement, payment or invoice fields. The summary cards at the top are the order number and the shopping cart serial number.
- Updated only while the order is ready to ship: the system only fetches Yahoo SCM orders that are ready to ship and refreshes the detail at the same time; changes on Yahoo after the order ships or is cancelled are not written back.
- All amounts are per item: the selling price, suggested retail price, each discount and the costs list one row per item, labeled with Yahoo's product ID; Yahoo has no order total or shipping fee field.
- Discounts are stored as returned: coupon, promotion, shopping credit, bonus point, welfare credit and OPENPOINT discounts are listed as Yahoo returns them; Yahoo's documentation does not say who bears them.
- Cost: "Product cost subtotal" is stored as Yahoo returns it; Yahoo's documentation does not say whether it equals the amount Yahoo pays you.
Order amounts
Available as soon as the order is fetched into Vanta and updated by later order syncs. Yahoo SCM only provides per-item prices and discounts; it has no shipping fee or order total.
| Field | Name | Yahoo SCM field | When available |
|---|---|---|---|
order.ProductPrice | Selling price The product selling price (商品售價), one row per item in Yahoo's order, labeled with the product ID. | Products[].ProductPrice(label: Products[].Id)Ready-to-ship order query( GetPreparingOrders) | Available as soon as the order is fetched into Vanta. |
order.RetailPrice | Suggested retail price The suggested retail price of the product (商品建議售價), one row per item in Yahoo's order, labeled with the product ID. | Products[].RetailPrice(label: Products[].Id)Ready-to-ship order query( GetPreparingOrders) | Available as soon as the order is fetched into Vanta. |
| Discounts and deductions | |||
order.CouponAmount | Coupon discount The coupon campaign discount amount (折價券活動折抵金額), one row per item labeled with the product ID; the documentation does not say who bears it. | Products[].CouponAmount(label: Products[].Id)Ready-to-ship order query( GetPreparingOrders) | Available as soon as the order is fetched into Vanta. |
order.ActivityAmount | Promotion discount The promotion campaign discount amount (促銷折價活動折抵金額), one row per item labeled with the product ID; the documentation does not say who bears it. | Products[].ActivityAmount(label: Products[].Id)Ready-to-ship order query( GetPreparingOrders) | Available as soon as the order is fetched into Vanta. |
order.RedeemAmout | Shopping credit The amount the buyer paid with Yahoo shopping credit (消費者YAHOO購物金折抵金額; the field name keeps Yahoo's spelling RedeemAmout), one row per item labeled with the product ID; the documentation does not say who bears it. | Products[].RedeemAmout(label: Products[].Id)Ready-to-ship order query( GetPreparingOrders) | Available as soon as the order is fetched into Vanta. |
order.RewardAmount | Bonus points The amount the buyer paid with Yahoo bonus points (消費者YAHOO超贈點折抵金額), one row per item labeled with the product ID; the documentation does not say who bears it. | Products[].RewardAmount(label: Products[].Id)Ready-to-ship order query( GetPreparingOrders) | Available as soon as the order is fetched into Vanta. |
order.WelfareAmount | Welfare credit The amount the buyer paid with Yahoo welfare credit (消費者YAHOO福利金折抵金額; the documentation notes this discount is no longer offered), one row per item labeled with the product ID; the documentation does not say who bears it. | Products[].WelfareAmount(label: Products[].Id)Ready-to-ship order query( GetPreparingOrders) | Available as soon as the order is fetched into Vanta. |
order.OpenPointAmount | OPENPOINT discount The amount the buyer paid with OPENPOINT points (消費者OpenPoint折抵金額), one row per item labeled with the product ID; the documentation does not say who bears it. | Products[].OpenPointAmount(label: Products[].Id)Ready-to-ship order query( GetPreparingOrders) | Available as soon as the order is fetched into Vanta. |
Reconciliation keys
Available as soon as the order is fetched into Vanta.
| Field | Name | Yahoo SCM field | When available |
|---|---|---|---|
order.OrderCode | Yahoo order number The order number (訂單編號); the Vanta order number is also taken from this field. | OrderInfo.OrderCodeReady-to-ship order query( GetPreparingOrders) | See category note |
order.ExternOrderkey | Shopping cart serial number The shopping cart serial number (購物車序號). | OrderInfo.ExternOrderkeyReady-to-ship order query( GetPreparingOrders) | See category note |
Cost
Available as soon as the order is fetched into Vanta; costs are the product costs returned by Yahoo SCM.
| Field | Name | Yahoo SCM field | When available |
|---|---|---|---|
order.Cost | Product cost The product cost (商品成本), one row per item labeled with the product ID. | Products[].Cost(label: Products[].Id)Ready-to-ship order query( GetPreparingOrders) | Available as soon as the order is fetched into Vanta. |
order.Subtotal | Product cost subtotal The product cost subtotal (商品成本小計), one row per item labeled with the product ID; the documentation does not say whether it equals the amount Yahoo pays the seller. | Products[].Subtotal(label: Products[].Id)Ready-to-ship order query( GetPreparingOrders) | Available as soon as the order is fetched into Vanta. |
16. MO Plus
MO Plus has fields in four categories: Order amounts, Payment, Tax & invoice and Reconciliation keys; the MO Plus API has no Seller settlement or Cost fields (see the reports in the MO Plus vendor center for settlements). All of them come from the same MO Plus order query API used to fetch orders (OrderQuery); the summary cards at the top are "Order item status" and "Invoice number".
- An order is a list of product lines: MO Plus splits an order into product lines, and shipping is one of them (product type "運費"). Each entry of "Product line amounts" is labeled with the vendor product number and excludes the shipping line; the shipping line's amount is listed separately as "Shipping line amount". The other per-line fields (item status, taxable, invoice, delivery number) follow the order MO Plus returns, include the shipping line, and line up position by position with "Order item sequence numbers"; a position without a value shows -.
- Amounts are stored as returned: MO Plus docs do not say whether a product line's order amount is the unit price or the line subtotal, and there are no discount or order total fields, so the system does not derive or add anything.
- Shipping fee: the order's own shipping fee still comes from the shipping line as before; this tab only lists the raw value and never changes the order.
- Item status as returned: "Order item status" is MO Plus's raw text (e.g. 訂單接獲(未付款), order received and unpaid); the system does not derive a payment status from it.
- Company invoices: the invoice tax ID and company name the buyer entered go to the order's invoice details (only empty fields are filled; values the warehouse entered are kept) and are not listed on this tab.
- Updated with order fetching: the system only fetches unshipped MO Plus orders, so delivery numbers or invoices that appear after shipment usually never arrive.
- Personal data: MO Plus shows "Purchaser name" only for unshipped home delivery orders and masks it otherwise; it is cleared when the order is de-identified.
Order amounts
Available as soon as the order is fetched into Vanta. MO Plus has no discount or order total fields, so amounts are listed per product line.
| Field | Name | MO Plus field | When available |
|---|---|---|---|
| Item amounts | |||
order.listItem_orderAmount | Product line amounts Order amount of each product line, as the vendor product number (entpGoodsNo) and the amount, in the order MO Plus returns them, excluding the line whose product type (goodsType) is "運費" (shipping). MO Plus docs do not say whether it is the unit price or the line subtotal, and the docs example only has an amount on the first item. | listItem[].orderAmount(label: listItem[].entpGoodsNo)Order query( OrderQuery) | Available as soon as the order is fetched into Vanta. |
| Shipping | |||
order.shipping_orderAmount | Shipping line amount Order amount of the line whose product type (goodsType) is "運費" (shipping). The order's shipping fee uses this value. | listItem[].orderAmountOrder query( OrderQuery) | Available only when the MO Plus order has a shipping line. |
Payment
| Field | Name | MO Plus field | When available |
|---|---|---|---|
order.listItem_itemStatus | Order item status Order item status as returned by MO Plus (e.g. 訂單接獲(未付款) - order received (unpaid), 出貨通知(已付款) - shipping notice (paid)); one value per line, in the order MO Plus returns them and in the same positions as the order item sequence numbers (including the shipping line). | listItem[].itemStatusOrder query( OrderQuery) | Available as soon as the order is fetched into Vanta. |
Tax & invoice
Available as soon as the order is fetched into Vanta; the invoice number, date and amount appear once the invoice is issued.
| Field | Name | MO Plus field | When available |
|---|---|---|---|
order.listItem_taxable | Taxable Taxable flag as returned by MO Plus: true = taxable, false = tax-exempt; one value per line, in the same positions as the order item sequence numbers (including the shipping line). | listItem[].taxableOrder query( OrderQuery) | Available as soon as the order is fetched into Vanta. |
order.listItem_invoiceAmount | Invoiced amount Invoiced amount; one value per line, in the same positions as the order item sequence numbers (including the shipping line). | listItem[].invoiceAmountOrder query( OrderQuery) | Available only after the invoice is issued. |
order.listItem_invoiceNo | Invoice number Invoice number; one value per line, in the same positions as the order item sequence numbers (including the shipping line). | listItem[].invoiceNoOrder query( OrderQuery) | Available only after the invoice is issued. |
order.listItem_invoiceDate | Invoice date Invoice date, stored as the raw MO Plus string (MO Plus docs do not state its format or time zone); one value per line, in the same positions as the order item sequence numbers (including the shipping line). | listItem[].invoiceDateOrder query( OrderQuery) | Available only after the invoice is issued. |
Reconciliation keys
| Field | Name | MO Plus field | When available |
|---|---|---|---|
order.orderNo | MO Plus order number Order number (the order number in Vanta). | orderNoOrder query( OrderQuery) | Available as soon as the order is fetched into Vanta. |
order.listItem_orderSeq | Order item sequence numbers Order item sequence number (e.g. 001), in the order MO Plus returns them (including the shipping line); the order number plus the sequence number is MO Plus's 18-digit order number-sequence code. | listItem[].orderSeqOrder query( OrderQuery) | Available as soon as the order is fetched into Vanta. |
order.listItem_deliveryNo | Delivery numbers Delivery number; one value per line, in the same positions as the order item sequence numbers (including the shipping line). | listItem[].deliveryNoOrder query( OrderQuery) | Available only after shipment, once there is a delivery number; the system only fetches unshipped MO Plus orders, so delivery numbers assigned after shipment usually never arrive. |
order.purchaser_name | Purchaser name Purchaser name, taken from the first line (the purchaser is order-level data that MO Plus docs list on every line). | listItem[].customerNameOrder query( OrderQuery) | MO Plus shows it only for home delivery orders that are not yet shipped and masks it otherwise (e.g. 謝○佑); cleared when the order is de-identified. |
17. PChome
PChome fields fall into three categories: Seller settlement, Reconciliation keys and Cost. All of them come from the order detail the system already fetches; no other API is called. PChome orders are supplier transfer orders: the order detail has product costs but no selling prices, and no payment or invoice data, so Order amounts, Payment and Tax & invoice are not shown. The summary cards at the top show the cost subtotal and the shipment number.
- Updated only until PChome confirms the shipment: each scheduled order sync re-reads PChome orders transferred in the last 7 days that PChome has not yet confirmed as shipped and updates them; changes after PChome confirms the shipment (or marks the order as not to be shipped) are not written back.
- The billing date is usually empty: "Billing date" is a date PChome provides only after it confirms the shipment, and the scheduled order sync no longer reads confirmed orders, so this field usually has no value; it shows the date string PChome returns (e.g. 2015/01/15).
- Costs as returned by PChome: each PChome order has a single item; "Unit cost" is that item's unit cost and "Cost subtotal" is the cost subtotal PChome returns (unit cost × ordered quantity). The PChome documentation does not say whether the cost subtotal is the amount payable to the vendor.
- The purchaser is personal data: "Purchaser name" and "Purchaser phone" are stored after the system decrypts PChome's encrypted fields, using the mobile number when there is no phone number; they are cleared when the order is de-identified and are not restored by later order syncs.
Seller settlement
The billing date appears once PChome confirms the shipment; Vanta's scheduled order sync no longer reads orders PChome has confirmed as shipped, so this field is usually empty. The PChome transfer order API has no fee or commission fields.
| Field | Name | PChome field | When available |
|---|---|---|---|
order.ShipDate | Billing date Shipment confirmation date (per the PChome documentation, the shipment confirmation date, i.e. the billing date), stored as the date string PChome returns (e.g. 2015/01/15). | ShipDateOrder detail( order) | Available once PChome confirms the shipment; Vanta's scheduled order sync no longer reads orders PChome has confirmed as shipped, so it is usually empty. |
Reconciliation keys
Available as soon as the order is fetched into Vanta; the shipment number appears once the shipment is written back to PChome.
| Field | Name | PChome field | When available |
|---|---|---|---|
order.Id | PChome order number PChome order number (e.g. 20150114090784-01); also used as the Vanta order number. | IdOrder detail( order) | Available as soon as the order is fetched into Vanta. |
order.ShipInfoShipId | Shipment number Shipment number (per the PChome documentation, SP or sp when the vendor ships by itself). | ShipInfo.ShipIdOrder detail( order) | Available once the shipment is written back to PChome. |
order.purchaser_name | Purchaser name Purchaser name (per the PChome documentation, the purchaser's name, transmitted encrypted; note that the purchaser's surname is in plain text), stored after Vanta decrypts it. Cleared when the order is de-identified. | Buyer.NameOrder detail( order) | Available as soon as the order is fetched into Vanta. |
order.purchaser_phone | Purchaser phone Purchaser phone number, falling back to the mobile number when there is no phone number (per the PChome documentation, the purchaser's Tel and Mobile, transmitted encrypted), stored after Vanta decrypts it. Cleared when the order is de-identified. | Buyer.TelOrder detail( order) | Available as soon as the order is fetched into Vanta. |
Cost
Available as soon as the order is fetched into Vanta. PChome transfer orders provide costs only, not selling prices.
| Field | Name | PChome field | When available |
|---|---|---|---|
order.ProdCost | Unit cost Unit cost of the product (per the PChome documentation, the unit cost in the product information); each PChome order has a single item, see the order items for the quantity. | Prod.CostOrder detail( order) | Available as soon as the order is fetched into Vanta. |
order.TotalCost | Cost subtotal Cost subtotal (per the PChome documentation, unit cost × ordered quantity); the documentation does not say whether it equals the amount payable to the vendor. | TotalCostOrder detail( order) | Available as soon as the order is fetched into Vanta. |
18. ETMall
ETMall fields fall into three categories: Order amounts, Reconciliation keys and Cost, all taken from the shipment management query the order fetch already calls, with no extra API call; ETMall has no seller settlement, payment or invoice fields. The summary cards at the top are the ETMall order number and the selling price total.
- Updated only while the order is ready to ship: the system only fetches ETMall orders in the "shipment instructed" status and refreshes the detail at the same time; changes on ETMall after the order ships or is cancelled are not written back.
- All amounts are per item: the selling price and the cost list one row per item, labeled with ETMall's order item number; ETMall has no shipping fee, discount or order total field.
- "Selling price total" is calculated by Vanta: the sum of selling price × quantity over the items, with the same formula as the order total. ETMall's documentation does not say whether the selling price is a unit price or a line subtotal; the order fetch treats it as the unit price.
- Cost: stored as ETMall returns it; ETMall's documentation does not say whether it is per unit or per line, nor how it relates to the product cost price and commission.
- Reconciliation keys: the delivery order number, channel name and delivery store number are taken from the order's first item; the delivery store number is in fact the pickup store code, the same as the order's pickup store.
Order amounts
Available as soon as the order is fetched into Vanta and updated by later order syncs. ETMall only provides the per-item selling price; it has no shipping fee, discounts or order total, so the sum is calculated by Vanta from the items.
| Field | Name | ETMall field | When available |
|---|---|---|---|
order.price | Selling price The product selling price (商品售價), one row per item in ETMall's order, labeled with the order item number (itemID); the documentation does not say whether it is a unit price or a line subtotal, and Vanta treats it as the unit price times quantity when calculating the order total. | data[].price(label: data[].itemID)Shipment management query( Search) | Available as soon as the order is fetched into Vanta. |
order.price_total | Selling price total Sum of price × qty over the items (calculated by Vanta with the same formula as the order total written at fetch); ETMall has no order total field, and the documentation does not say whether price is a unit price or a line subtotal. | data[].price × data[].qtyShipment management query( Search) | Available as soon as the order is fetched into Vanta. |
Reconciliation keys
Available as soon as the order is fetched into Vanta.
| Field | Name | ETMall field | When available |
|---|---|---|---|
order.orderID | ETMall order number The order number (訂單編號); the Vanta order number is also taken from this field. | data[].orderIDShipment management query( Search) | See category note |
order.itemID | Order item numbers The order item numbers (訂單項次), one per item in ETMall's order; shipment status is reported back to ETMall per item number. | data[].itemIDShipment management query( Search) | See category note |
order.deliveryOrderID | Delivery order number The delivery order number (配送單號), taken from the order's first item row; the shipping number of store-pickup orders is also taken from this field. | data[].deliveryOrderIDShipment management query( Search) | See category note |
order.chName | Channel name The channel name (通路名稱), taken from the order's first item row. | data[].chNameShipment management query( Search) | See category note |
order.storeName | Delivery store number The delivery store number (配送店號), taken from the order's first item row; the Vanta order's pickup store code is also taken from this field. | data[].storeNameShipment management query( Search) | See category note |
Cost
Available as soon as the order is fetched into Vanta; costs are the values returned by ETMall.
| Field | Name | ETMall field | When available |
|---|---|---|---|
order.cost | Cost The cost (成本), one row per item labeled with the order item number (itemID); the documentation does not say whether it is per unit or per line, nor how it relates to the product-level cost price and commission. | data[].cost(label: data[].itemID)Shipment management query( Search) | Available as soon as the order is fetched into Vanta. |
19. momo
momo fields fall into four categories: Order amounts, Tax & invoice, Reconciliation keys and Cost. All of them come from the unshipped-order queries the system already runs (vendor delivery, convenience store and third-party logistics); no other API is called. momo has no Seller settlement or Payment fields. The summary cards at the top show the sale price total and the invoice number.
- Updated only while the order is unshipped on momo: the system only fetches momo orders that have not shipped and refreshes the details each time; changes after shipment are not written back. When some sub-orders of an order ship first, the tab keeps the data of all sub-orders from the last fetch before shipment instead of showing only the unshipped ones.
- One order can be made up of several momo sub-orders: momo splits a parent order into sub-orders, and the system combines the sub-orders of the same parent order into one order. Sale and purchase prices are listed one row per sub-order in the order momo returns them, labeled with the sub-order number; invoice, order number, delivery slip number and pickup store hold one value per sub-order, and the same position is the same sub-order.
- Sale and purchase prices are momo's raw values: momo docs only say "sale price (tax included)" and "purchase price (tax included)" without saying whether they are per unit or per line. "Sale price total" is the sum of each sub-order's sale price times its quantity, the same calculation as the order total.
- Invoices are issued by momo: the invoice number and date are shown as momo sends them and are empty until the invoice is issued.
- Delivery slip number and pickup store exist only on some orders: the delivery slip number is only on vendor-delivered orders and the pickup store only on convenience store pickup orders.
- The purchaser name is personal data: "Purchaser name" is cleared when the order is de-identified; on convenience store and third-party logistics orders momo only sends a masked name. momo does not provide the purchaser's phone number.
Order amounts
Available as soon as the order is fetched into Vanta.
| Field | Name | momo field | When available |
|---|---|---|---|
order.salePrice | Sale price (tax incl.) Sale price (tax included) of each sub-order with its order number (completeOrderNo), in the order momo returns them; momo docs do not say whether it is per unit or per line. | dataList[].salePrice(label: dataList[].completeOrderNo)Unshipped order query( OrderServlet.do) | See category note |
order.salePrice_sum | Sale price total Sum of each sub-order's sale price (tax included, salePrice) times its quantity (syslast); the same calculation as the Vanta order total (salePrice taken as the unit price). | dataList[].salePriceUnshipped order query( OrderServlet.do) | See category note |
Tax & invoice
Available once momo issues the invoice.
| Field | Name | momo field | When available |
|---|---|---|---|
order.invoiceNo | Invoice number Invoice number; one value per sub-order, in the order momo returns them. Invoices are issued by momo. | dataList[].invoiceNoUnshipped order query( OrderServlet.do) | See category note |
order.invoiceDate | Invoice date Invoice date, stored as the raw momo string (e.g. 2026/02/10); one value per sub-order, in the order momo returns them. | dataList[].invoiceDateUnshipped order query( OrderServlet.do) | See category note |
Reconciliation keys
Available as soon as the order is fetched into Vanta; the delivery slip number exists only on vendor-delivered orders and the pickup store only on convenience store orders.
| Field | Name | momo field | When available |
|---|---|---|---|
order.completeOrderNo | momo order number Order number (momo's sub-order number); one value per sub-order, in the order momo returns them. | dataList[].completeOrderNoUnshipped order query( OrderServlet.do) | Available as soon as the order is fetched into Vanta. |
order.slipNo | Delivery slip number Delivery slip number; one value per sub-order, in the order momo returns them. | dataList[].slipNoUnshipped order query( OrderServlet.do) | Only vendor-delivered orders have this field. |
order.storeIdName | Pickup store Pickup store; one value per sub-order, in the order momo returns them. | dataList[].storeIdNameUnshipped order query( OrderServlet.do) | Only convenience store pickup orders have this field. |
order.purchaser_name | Purchaser name Purchaser name; taken from the first sub-order's custNameMask (masked value on convenience store and third-party logistics orders), or custName (vendor delivery) when absent. Cleared when the order is de-identified. | dataList[].custNameMaskUnshipped order query( OrderServlet.do) | Available as soon as the order is fetched into Vanta. |
Cost
Available as soon as the order is fetched into Vanta.
| Field | Name | momo field | When available |
|---|---|---|---|
order.buyPrice | Purchase price (tax incl.) Purchase price (tax included) of each sub-order with its order number (completeOrderNo), in the order momo returns them; momo docs do not say whether it is per unit or per line. | dataList[].buyPrice(label: dataList[].completeOrderNo)Unshipped order query( OrderServlet.do) | See category note |
20. FAQ
▪ The tab shows "No platform data"?
The platform details for this order have not been fetched yet. Common reasons: Shopee's order income API did not respond during the fetch (the order is still created and the next fetch fills the details in), or the order had already shipped before this feature went live (the system only fetches Shopee, Shopline, FreeStore, EasyStore and Yahoo SCM orders that are ready to ship, ETMall orders in the shipment instructed status, Coupang orders whose payment is completed, Ruten orders that are to be confirmed or ready to ship, PChome orders that PChome has not yet confirmed as shipped, BVSHOP, 1shop and momo orders that have not shipped and WooCommerce orders that are processing, so shipped orders are not filled in).
▪ "Escrow amount" differs from the actual payout in Shopee?
The value here is Shopee's pre-shipment estimate. Refunds, adjustments and the final settlement after shipment are not written back; use Shopee's payout records for reconciliation.
▪ Do duplicated orders show platform details?
No. A duplicated order is detached from the platform, carries no platform details and does not show this tab; the original order's details are unaffected.
▪ Can platform details be changed through the API?
No. Platform details are written only by order fetching; neither Partners API order create/update nor an App's order metadata can change them.
21. Related features
- Platform Comparison: how each platform connects and fetches orders
- Order details (warehouse)
- Order details (merchant)