Sales Orders

Note: Multi-fulfilment is supported, but behaviour can be strange if edited. Caution must be exercised when attempting multi-fulfilment.

Driver Name - Dear Inventory New Order Webhook

  1. To pull sales orders, the Sale has been picked notification type must be selected in Cin7 Core.

    The Pick List is used.

  2. Open sync.

    This will synchronise jobs to .wms by taking the TaskID sent in the connection and making a call to the sale / fulfilment endpoint in Cin7 Core.

    Tip:  To re-sync, undo and re-authorise the pick.

.wms field

Cin7 field

Notes

InstanceCode

connections.DWMSInstance

Sourced from ERPGate

TenantCode

connections.DWMSDefaultTenant

Sourced from ERPGate

WarehouseCode

Lines/location

Ability to map using DEAR.WarehouseMap

APIKey

connections.DWMSAPIKey

Sourced from ERPGate

OrderSource

NA

Hardcoded to Cin7 Core API (Sales)

PackSlipNumber

<SalesOrderNumber>.<FulfilmentNumber>

Combination of 2 fields

ParentCustomerCode

NA

Harcoded to CUSTOMER

CustomerCode

Customer

 

OrderNumber

CustomerReference

 

OrderDate

SalesOrderDate

 

PackingSlipURL

NA

Hardcoded to INTERNAL

CarrierServiceCode

dependent on mapping

Refer to carrier settings.

DeliveryName

Concatenation of company/contact, falls back to Customer

 

DeliveryAddress1

ShippingAddress/Line1

 

DeliveryAddress2

ShippingAddress/Line2

 

DeliverySuburb

ShippingAddress/City

 

DeliveryState

ShippingAddress/State

Switch case of full state name to shortened.

DeliveryPostcode

ShippingAddress/Postcode

 

DeliveryCountry

ShippingAddress/Country

Defaults to Australia unless overridden by a setting.

DeliveryEmail

Email

 

DeliveryPhone

Phone

 

Additional01

SaleID

 

Additional02

TaskID

 

Additional03

NA

Hardcoded to SALESORDER

Additional04

NA

Reserved for custom work.

Additional05

NA

Reserved for custom work.

Additional06

setting defined

Refer to settings.

Additional07

AdditionalAttribute7

These are synchronised under all circumstances. ENG 10228

 

 

Additional08

AdditionalAttribute8

Additional09

AdditionalAttribute9

Line/ItemCode

Lines/SKU

 

Line/Quantity

Lines/Quantity

 

Line/UnitValueAmount

Lines/Price

 

The following settings can be applied to change the logic and translation:

Setting

Values

Notes

Dear.Shipping.CarriersToIgnore

JSON array

Default - empty array

Ignores orders with these carrier set in DEAR (before mapping).

DEAR.WarehouseMap

JSON object

Default - empty object

A key value pairing mapping the jobs to the correct warehouse.

Dear.Shipping.UseCarrierFromNoteField

Yes/No

Default - No

Maps the carrier from the Note field instead of the Carrier field.

Dear.Shipping.UseCarrierField

Yes/No

Default - No

Use the Carrier field to map.

This is usually manually set to Yes.

DEAR.Additional06

null

Sets Additional06 to a specific field.

DEAR.PackerMessageField

"Note"

Sets the PackerMessage to a specific field.

DEAR.FreightSpecialInstructionsField

null

Sets the FreightSpecialInstructions to a specific field.

DEAR.ShowSalesRepresentative

Yes

Synchronises the Sales Representative to a comment.

DEAR.ShowPaymentTerms

Yes

Synchronises the Payment Terms to a comment.

Driver Name - Dear Inventory Fulfilments Complete

On completion of a sales order, a connection can be set up to push the data to Cin7.

The Cin7 process is:

  • filling in and authorising the Pack stage.

  • filling in and authorising the Ship stage.

The connector uses either the PackManifestSummary export or the PackManifestXML export. The difference between the 2 is due to box tracking and how it completes.

Use the PackManifestXML export if:

  • the customer wishes to know what was in what box

  • partial shipping is required.

Tip:  Do not use PackManifestSummary if you require partial shipping. If you do, the entire shipment will be shipped.

This is controlled by the Dear.Shipping.CompletionDocumentType setting.

When addressing the API, the following fields are used to direct the correct ID when updating data:

Cin7 field

Pack Manifest field

Pack Manifest Summary field

SaleID

Additional01

Additional01

TaskID

Additional02

Additional02

If begins by processing a Pack, using the field map below, in a Pack/Lines element.

Note: The BoxNumbers are affected by Dear.Shipping.ShipmentPackType which defaults to BoxNumbers.

Cin7 field

Pack Manifest field

Pack Manifest Summary field

Box

BoxNumbers - incremental box numbers

Else - SSCC

Always 1

Location

WarehouseCode

NA - copied from pick

Quantity

QuantityShipped

NA - copied from pick

SKU

ItemCode

NA - copied from pick

Once at the Ship stage, the relevant boxes are marked as shipped with the below fields mapped in a Ship/Lines element:

Cin7 field

Pack Manifest field

Pack Manifest Summary field

Box

BoxNumbers / SSCC

1

Carrier

CarrierServiceCode

CarrierServiceCode

IsShipped

true

True

TrackingNumber

CarrierConnote

ConnoteNumber

The following settings can be applied to the connection:

Setting

Values

Notes

Dear.Shipping.CompletionDocumentType

PackManifestSummary/PackManifestXML

Changes the put behaviour based on the above.

Dear.Shipping.ShipmentPackType

BoxNumbers/SSCCs

Changes the box reference based on the above.

Dear.CarrierServiceMap

JSON Map {“CarrierServiceCode”:”Carrier”}

Maps the carrier from .wms to a generic carrier in Cin7.

DEAR.WarehouseMap

JSON Map {“WarehouseCode”:”Location”}

A reverse map for WarehouseCode to Cin7 Location.

Driver Name - Dear Inventory Order Void Webhook

This connection cancels any open jobs for this order. There are no settings, only the default mapping.

.wms field

Cin7 field

Notes

APIKey

connections.DWMSAPIKey

Sourced from ERPGate

InstanceCode

connections.DWMSInstance

Sourced from ERPGate

PackSlipNumber

concatenation of SalesOrderNumber.FulfilmentNumber

 

TenantCode

connections.DWMSDefaultTenant

Sourced from ERPGate

WarehouseCode

left blank