Sync Order-Level Custom Fields to Quivers

In This Article

• Overview
• How to Set Up Order-Level Custom Field Sync
• Where Synced Fields Appear
• Troubleshooting
• Frequently Asked Questions

Overview

Who Is This For?

This article is for Sellers and integration partners who use custom data fields on orders in their e-commerce platform or ERP and want those fields to sync into Quivers at the order level.

What Are Order-Level Custom Fields?

Quivers supports order-level custom fields in addition to the existing item-level (OPV) custom fields. If your e-commerce platform or order management system passes custom data at the order level — such as purchase order numbers, customer account codes, or internal reference tags — those values can be captured and stored in Quivers alongside the order record. This makes it easier to reconcile orders across systems without losing order-level metadata.

How It Works

• Order-level custom fields sync to Quivers the same way item-level (OPV) custom fields do — as name/value pairs sent along with the order.
• When an order is created or synced, any custom field values attached to the order object in your platform (rather than to an individual line item) are passed to Quivers and stored on the order record.
• Each field needs both a name and a string value. If a field is sent with a missing or empty value, Quivers silently drops it — the order still syncs normally, but that field won't appear anywhere on the record, and no error is returned.
• Synced fields are then accessible in the Order Details Panel, as well as in order exports and reporting, alongside item-level fields.

Why It Matters

Order-level custom fields give Sellers and integration partners a way to keep order-level metadata — like PO numbers or account codes — attached to the order record itself, without relying on a spreadsheet or a separate system to reconcile it later.

How to Set Up Order-Level Custom Field Sync

Complete the steps below in order. Reach out to support@quivers.com if you need help at any point.

Prerequisites

✓ Quivers integration active with your e-commerce platform or ERP.

✓ Order-level custom fields defined and populated in your platform — not at the line-item level.

✓ Custom field sync enabled for your account by your Quivers implementation team.

Step 1: Define Your Custom Fields

In your e-commerce platform or order management system, ensure the custom fields you want to sync are defined at the order level (not at the line-item level). Common examples include:

• Purchase order (PO) number
• Customer account code
• Internal order reference
• Sales territory or region

Step 2: Confirm Field Mapping With Your Implementation Team

1. Contact your Quivers implementation team or CSM to map your order-level custom fields to the corresponding fields in Quivers.
2. Confirm which fields will be synced, and how each one appears in Quivers order records.
3. Confirm that your integration sends a string value for every custom field it passes. A field sent without a value is dropped silently — it won't sync, and no error is returned — so it's worth double-checking with your integration team before go-live.

Step 3: Verify the Sync

1. Place a test order with custom field values populated at the order level.
2. In your Quivers admin, open the order and go to the Order Details Panel.
3. Confirm the custom field values appear correctly on the order record.

Where Synced Fields Appear

Once synced, order-level custom fields show up in the same place as item-level (OPV) custom fields:

• Synced order-level custom fields display in the Order Details Panel, alongside any item-level (OPV) custom fields already on the order.
• Fields are shown as concatenated “Name: Value” strings.
• If an order has multiple custom fields, they're listed together in this same location.

Troubleshooting

If a custom field isn't syncing as expected, work through the checks below.

1. Custom Field Isn't Appearing on the Order

• Confirm your platform is sending a non-empty string value for the field — missing or empty values are silently dropped and won't trigger an error.
• Confirm the field is attached to the order object in your platform, not to an individual line item.
• Confirm your Quivers implementation team has enabled custom field sync for your account and mapped the specific field you're sending.

2. Field Appears as an Item-Level (OPV) Field Instead

• Confirm the value is populated at the order level in your platform, not on a line item — item-level values sync as OPV custom fields instead of order-level ones.

3. Values Look Cut Off or Combined Oddly

• This is expected — Quivers currently displays custom fields as combined “Name: Value” strings in the Order Details Panel. Contact support@quivers.com if something looks wrong beyond that formatting.

Frequently Asked Questions

What's the difference between order-level and item-level custom fields?

Item-level (OPV) custom fields are attached to individual order line items. Order-level custom fields apply to the entire order — for example, a PO number that covers all items in the order.

What happens if a custom field is sent without a value?

Quivers silently ignores it. The order still syncs normally, but that field won't appear on the record, and no error is returned. It's worth placing a test order to confirm your integration always sends a value before you rely on a field in production.

Can I use order-level custom fields in exports or reports?

Yes — custom fields synced to Quivers are available in order data exports. Contact support for specific reporting needs.

Is there a limit on how many custom fields I can sync?

Contact your Quivers CSM for information on field limits for your account configuration.