Import eBay orders
Lesson 13 of 30 6 min read
Choose which eBay orders come in by fulfilment status, assign the customer and Location, and carry extra order data as tags.
eBay is a marketplace: eBay owns the buyer, the listing and, often, the tax. The connector offers Order, Inventory and Shipment Configurations. This lesson covers the order basics. The next covers the part that takes real thought, which is tax.
By the end of this lesson you'll be able to configure which eBay orders are imported and how they're attributed in the back office.
The shared setting
| setupDate | Applies to every eBay Document type. Only documents created on or after this date are imported, so history isn't pulled in at go-live. Set automatically. |
|---|
Which orders?
| orderFulfillmentStatus | Default NotStartedOrInProgress. Only orders in this fulfilment status are eligible for import. |
|---|---|
| lastImportDate | The watermark, managed by the system. |
The default picks up orders that still need shipping, which is what a back office or warehouse wants. You'd rarely change it.
Who and where?
| defaultCustomerId | The Party used when no customer can be identified from the order. |
|---|---|
| alwaysSetDefaultCustomerId | Use the default customer for every order, whatever the order says. |
| fulfillmentLocationId | The Location assigned to every imported eBay order. |
Most eBay sellers book all eBay sales to a single customer in the ERP, such as "eBay UK". If that's
the case, set defaultCustomerId and turn on alwaysSetDefaultCustomerId. The buyer's name and
delivery address still travel on the order for the warehouse.
Good to know
The buyer's delivery address travelling with the order is how commerce imports generally work, but the eBay guide doesn't spell it out. Check a test order's Document before go-live.
Extra data as tags
| documentLevelTagGeneration | Rules that create tags from fields on the eBay order. Each rule has a key, a path to the source field and an optional source. |
|---|---|
| documentLevelAdvancedTagGeneration | The same, using JSON Path or JSON Pointer expressions for nested data. |
Typical uses: tagging the eBay marketplace an order came from, or the shipping service the buyer chose, so a later Mapping filter or tag map can act on it.
Hilltop Coffee on eBay UK and eBay Germany
Hilltop Coffee lists on eBay UK and ships some orders to buyers on eBay Germany. The ERP has one "eBay" customer.
orderFulfillmentStatusstays atNotStartedOrInProgress.defaultCustomerIdis the "eBay" Party withalwaysSetDefaultCustomerIdon.fulfillmentLocationIdis the roastery.- A tag generation rule writes the purchase marketplace as a tag, so finance can report UK and German sales separately.
Tax is next.
Recap
setupDateapplies to every eBay Document type.- Orders import from
NotStartedOrInProgressby default. - Most sellers use one default customer for all eBay sales.
- Tag generation rules carry eBay-specific details to later Mappings.
Quick guides for this topic
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.