Before you compare Sherpaan data

Confirm the intended connection, warehouse selections and mapping options through the Sherpaan setup guide. Separate product, supplier-product, order and line identities. Relationships resolve Sherpaan codes to the corresponding imported Optiply records.

Steps to compare Sherpaan data

  1. Choose the entity and transfer direction you need to check.
  2. Find its field in the matching table below.
  3. Compare the Sherpaan value with the corresponding Optiply record.
  4. Apply the warehouse, status and matching conditions for that entity.
  5. For received quantities, compare the purchase line as well as its receipt.

Fields in Sherpaan imports

Products: Sherpaan to Optiply

Optiply fieldSherpaan fieldMeaning or condition
remoteId, skuCodeItemCodeStable product reference and SKU.
nameDescriptionProduct description.
eanCodeEanCode.EanCodes.EanCodeItemInformationItem.EanCodeUses the single item, or the first item when several exist.
articleCodeBrandBrand value.
pricePriceProduct price.
stockLevelAvailableSum across selected warehouses, or selected warehouse-group stock.
assembledItemTypeTrue for Assembly, false for Stock. Only these two types are imported.
statusItemStatusActive becomes enabled. Other values become disabled.
createdAtRemoteDateAddedSource product creation date.

Stock uses Available, not the separate Stock value. Stock, sales and purchase warehouse selections are independent. Grouped stock uses the latest token per item.

Product compositions: Sherpaan to Optiply

Optiply fieldSherpaan fieldMeaning or condition
composedProductIdItemCodeAssembly product, resolved to its Optiply product.
partProductIdItemAssemblies.ItemAssembly.ItemCodeComponent product, resolved to its Optiply product.
partQuantityItemAssemblies.ItemAssembly.NumberComponent quantity, rounded to a whole number with a minimum of 1.
remoteIdAssembly item code + component item codeGenerated assembly-component identity.

Only Assembly records with composition information contribute components. Both products must already be matched.

Suppliers: Sherpaan to Optiply

Optiply fieldSherpaan fieldMeaning or condition
remoteIdSupplierCodeSupplier reference.
nameCompany + NameJoined with a space and trimmed.
userReplenishmentPeriodOrderPeriodConfigured supplier replenishment period.
deliveryTimeDeliveryPeriodSupplier lead time.
emailsEmailSupplier email addresses. Invalid email values are removed.

Supplier products: Sherpaan to Optiply

Optiply fieldSherpaan fieldMeaning or condition
remoteIdItemCode + _ + SupplierCodeProduct-supplier pair, not SupplierItemCode alone.
nameSupplierDescriptionSupplier's description.
skuCodeSupplierItemCodeSupplier SKU.
productIdItemCodeResolves to the imported Optiply product.
supplierIdSupplierCodeResolves to the imported Optiply supplier.
priceSupplierPriceNonnegative purchase price.
deliveryTimeDeliveryPeriodLead time unless this attribute is excluded from synchronization.
minimumPurchaseQuantityMinPurchaseQtyRounded whole quantity, minimum 1.
lotSizeSupplierPurchaseQtyRounded whole quantity, minimum 1.
freeStockSupplierStockSupplier availability, rounded and limited to nonnegative values.
preferredPreferredPreferred-supplier indication.
availabilityDateAvailableFromDate when the item becomes available.
statusSupplierItemStatusActive becomes enabled. Other values become disabled.

Supplier and supplier-product mappings can exclude specified attributes. Check the active mapping before expecting a lead-time change. Supplier-product lead time is limited to 365, with 0 treated as unset. New disabled products and supplier products are excluded.

Sales orders and lines: Sherpaan to Optiply

Entity and Optiply fieldSherpaan fieldMeaning or condition
Order remoteIdOrderNumberSource order identity.
Order totalValueOrderAmountInclVATOrder amount including VAT.
Order placedOrderDateOrder date.
Line remoteIdOrderNumber + _ + LineNumberSource line identity.
Line sellOrderIdOrderNumberMatched imported order.
Line productIdItemCodeMatched imported product.
Line quantityQuantityOrderedOrdered quantity.
Line subtotalValueAmountLine amount.

All sales statuses are included by default. When restricted, imports retain Processed and Cancelled records. Cancelled orders are marked for deletion. Existing sales orders and lines are not updated. New lines added to an existing order are not imported through the new-order route. Individual line deletions are not synchronized.

Purchase orders: Sherpaan to Optiply

Optiply fieldSherpaan fieldMeaning or condition
remoteIdPurchaseOrderNumberSource purchase-order identity.
supplierIdSupplierCodeMatched imported supplier.
placedPurchaseDatePurchase date. Only dates after January 1, 2025 are included.
totalValueSum of purchase-line AmountTotal of included lines.
completedLatest line ReceivedDateSet when total QuantityOrdered equals total QuantityReceived.

Orders need purchase lines and usable item codes. The purchase warehouse selection applies. Cancelled purchases are marked for deletion. Completion compares order-wide totals, not a separate equality test for every line.

Purchase lines and receipts: Sherpaan to Optiply

Entity and Optiply fieldSherpaan fieldMeaning or condition
Line remoteIdPurchaseOrderNumber + _ + ItemCodePurchase-line identity.
Line buyOrderIdPurchaseOrderNumberMatched imported purchase.
Line productIdItemCodeMatched imported product.
Line quantityQuantityOrderedOrdered quantity.
Line subtotalValueAmountPurchase-line amount.
Line expectedDeliveryDateDateExpectedExpected line delivery date.
Receipt remoteIdPurchaseOrderNumber + _ + ItemCodeSame source pair as the purchase line.
Receipt buyOrderLineIdSame purchase-number and item-code pairResolves to the imported purchase line.
Receipt quantityQuantityReceivedCurrent received quantity, not a separate receipt for each increase.
Receipt occurredReceivedDateReceipt date.

Receipts need a received date, positive quantity and a matched purchase line. An existing receipt updates when its quantity changes.

Purchase export preparation: Optiply to Sherpaan

Optiply prepares purchase orders with the source supplier reference and source product references. Lines carry quantity and a unit price calculated from subtotal divided by quantity. Support confirms the outbound warehouse and destination-field configuration during setup. Check the resulting purchase in Sherpaan before using it as confirmation of an export.

What you see when comparing Sherpaan data worked

You can match the product, supplier, order or line by its own identity. You can explain stock from the selected warehouses and receipts from the corresponding purchase line. Keep a field match separate from confirmation that an import or export completed.

Limits of comparing Sherpaan data

Codes from Sherpaan are matched to Optiply IDs, not copied as interchangeable database identifiers. A missing product, supplier or purchase relationship can exclude dependent lines. Existing sales changes and line deletions need a separate investigation. Purchase completion uses equal order totals, so offsetting differences between lines can satisfy that comparison.

If comparing Sherpaan data did not work

Check the entity, source code, warehouse selection and status first. For a missing purchase line, check its imported product and purchase. For a receipt, check received quantity and date. If the mismatch remains, contact Support through the setup guide. Provide the direction, field and comparison time without credentials. Do not recreate an order to test a mapping.