Ship Via and FOB use

I feel like Epicor needs a 3rd field. Not just FOB and Ship Via.

  1. If I were to use just Inco terms in FOB I would know where ownership is passed and who is responsible for what. e.g. Ex Works Origen or DDU.
  2. Ship Via tells me how to ship it. eg. UPS Ground etc.
  3. I still need a way to describe payments. e.g Prepay & Add, Collect, Third Party etc.
    We currently combine the Inco terms and the payment in our FOB but some orders then need a different FOB on different lines.
    How does everyone else handle this in E10? (or in Kinetic since we will be there Q1 '23)

Vote for Epicor Idea 143

Properly implement INCOTERMs (including v2020)

3 Likes

This has been a requirement on a couple of projects I’ve been on. We would create appropriate UD fields, some User Codes lists to populate them from, and changes to forms. I wasn’t involved if there were also BPMs for process changes.

@Mark_Wonsil you beat me to it. Incoterms is the answer. In fact, for some customers, we have entered the Incoterms table into the FOB Setup. Note that FOB is ONE of the Incoterms for international commerce. See Incoterms - Wikipedia for the complete list of Incoterms.

2 Likes

Isn’t that what the manifest pay flag field is for? we use it regardless of if we are using manifest (quick ship) for a shipment or not (we only have license for UPS)

1 Like

Agreed.
Manifest pay flag drives this functionally when using quickship or Agile.