Supply Lens

Set up Lenhams

Lesson 27 of 30 6 min read

Send orders to Lenhams with control over Unit of Measure conversion, and import shipments over AS2 with SKU and sequence-number safeguards.

Lenhams is a logistics provider that Supply Lens connects to over AS2. It's listed among the shipping integrations as "Lenham AS2". AS2 is a secure way of exchanging business documents directly between two companies' servers, common in EDI. Orders go to Lenhams, and shipments come back. The settings handle three things that matter on that route: pack sizes, variant SKUs and problem messages.

By the end of this lesson you'll be able to configure Lenhams orders and shipments and choose the right error behaviour.

Rendering diagram...

Orders: Unit of Measure conversion

fulfillmentLocationsDoNotConvertSupply Lens Location IDs whose orders are sent without Unit of Measure conversion. Useful where certain warehouses work in pack sizes that shouldn't be normalised.

By default, quantities are converted between Units of Measure on the way to Lenhams. If one of the customer's Locations already works in Lenhams' pack sizes, list it here so its quantities go as they are.

Shipments

neverUseParentSkuWhen true, the parent SKU is never used in place of a variant SKU on shipment lines, even if the variant has no SKU. When false or unset, the parent SKU may be used as a fallback.
commitSequenceNumberOnErrorWhen true, the AS2 sequence number is committed even if processing fails, so the same message isn't reprocessed on the next run. When false or unset, the sequence number isn't advanced on error.
importDelayWait before importing a shipment so other systems can change it first.
lastImportDateThe watermark, managed by the system.

Parent SKU fallback

If a variant has no SKU, using its parent's SKU might match the wrong Product. Turn on neverUseParentSku when parent SKUs aren't real, stockable Products in the back office.

Error behaviour

This is a genuine trade-off:

commitSequenceNumberOnErrorOn errorGood forRisk
Off (default)The message is retried next runTemporary problems that fix themselvesA message that can never succeed blocks or repeats
OnThe message is skipped next runAvoiding duplicate processing of a bad messageThe failed shipment must be dealt with by hand

Watch out

With it on, a failed shipment won't be retried automatically. Make sure someone watches for failed Documents so a skipped shipment doesn't go unnoticed.

Fern & Finch's pallet warehouse

Fern & Finch uses Lenhams for bulk stock and keeps a small pallet warehouse of its own.

  • The pallet warehouse already works in Lenhams' case sizes, so its Location goes in fulfillmentLocationsDoNotConvert.
  • Parent products in Unleashed aren't stockable, so neverUseParentSku is on.
  • After a malformed message was retried on every run for a day, the team turns on commitSequenceNumberOnError and adds a daily check of failed Documents.

Recap

  • Lenhams orders go out and shipments come back over AS2.
  • fulfillmentLocationsDoNotConvert sends listed Locations' quantities without conversion.
  • neverUseParentSku stops parent SKUs standing in for variants.
  • commitSequenceNumberOnError trades automatic retries for no repeated processing; watch for failures if you turn it on.
Complete and take the quiz

Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.