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
- Choose the entity and transfer direction you need to check.
- Find its field in the matching table below.
- Compare the Sherpaan value with the corresponding Optiply record.
- Apply the warehouse, status and matching conditions for that entity.
- For received quantities, compare the purchase line as well as its receipt.
Fields in Sherpaan imports
Products: Sherpaan to Optiply
| Optiply field | Sherpaan field | Meaning or condition |
|---|---|---|
remoteId, skuCode | ItemCode | Stable product reference and SKU. |
name | Description | Product description. |
eanCode | EanCode.EanCodes.EanCodeItemInformationItem.EanCode | Uses the single item, or the first item when several exist. |
articleCode | Brand | Brand value. |
price | Price | Product price. |
stockLevel | Available | Sum across selected warehouses, or selected warehouse-group stock. |
assembled | ItemType | True for Assembly, false for Stock. Only these two types are imported. |
status | ItemStatus | Active becomes enabled. Other values become disabled. |
createdAtRemote | DateAdded | Source 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 field | Sherpaan field | Meaning or condition |
|---|---|---|
composedProductId | ItemCode | Assembly product, resolved to its Optiply product. |
partProductId | ItemAssemblies.ItemAssembly.ItemCode | Component product, resolved to its Optiply product. |
partQuantity | ItemAssemblies.ItemAssembly.Number | Component quantity, rounded to a whole number with a minimum of 1. |
remoteId | Assembly item code + component item code | Generated assembly-component identity. |
Only Assembly records with composition information contribute components. Both products must already be matched.
Suppliers: Sherpaan to Optiply
| Optiply field | Sherpaan field | Meaning or condition |
|---|---|---|
remoteId | SupplierCode | Supplier reference. |
name | Company + Name | Joined with a space and trimmed. |
userReplenishmentPeriod | OrderPeriod | Configured supplier replenishment period. |
deliveryTime | DeliveryPeriod | Supplier lead time. |
emails | Email | Supplier email addresses. Invalid email values are removed. |
Supplier products: Sherpaan to Optiply
| Optiply field | Sherpaan field | Meaning or condition |
|---|---|---|
remoteId | ItemCode + _ + SupplierCode | Product-supplier pair, not SupplierItemCode alone. |
name | SupplierDescription | Supplier's description. |
skuCode | SupplierItemCode | Supplier SKU. |
productId | ItemCode | Resolves to the imported Optiply product. |
supplierId | SupplierCode | Resolves to the imported Optiply supplier. |
price | SupplierPrice | Nonnegative purchase price. |
deliveryTime | DeliveryPeriod | Lead time unless this attribute is excluded from synchronization. |
minimumPurchaseQuantity | MinPurchaseQty | Rounded whole quantity, minimum 1. |
lotSize | SupplierPurchaseQty | Rounded whole quantity, minimum 1. |
freeStock | SupplierStock | Supplier availability, rounded and limited to nonnegative values. |
preferred | Preferred | Preferred-supplier indication. |
availabilityDate | AvailableFrom | Date when the item becomes available. |
status | SupplierItemStatus | Active 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 field | Sherpaan field | Meaning or condition |
|---|---|---|
Order remoteId | OrderNumber | Source order identity. |
Order totalValue | OrderAmountInclVAT | Order amount including VAT. |
Order placed | OrderDate | Order date. |
Line remoteId | OrderNumber + _ + LineNumber | Source line identity. |
Line sellOrderId | OrderNumber | Matched imported order. |
Line productId | ItemCode | Matched imported product. |
Line quantity | QuantityOrdered | Ordered quantity. |
Line subtotalValue | Amount | Line 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 field | Sherpaan field | Meaning or condition |
|---|---|---|
remoteId | PurchaseOrderNumber | Source purchase-order identity. |
supplierId | SupplierCode | Matched imported supplier. |
placed | PurchaseDate | Purchase date. Only dates after January 1, 2025 are included. |
totalValue | Sum of purchase-line Amount | Total of included lines. |
completed | Latest line ReceivedDate | Set 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 field | Sherpaan field | Meaning or condition |
|---|---|---|
Line remoteId | PurchaseOrderNumber + _ + ItemCode | Purchase-line identity. |
Line buyOrderId | PurchaseOrderNumber | Matched imported purchase. |
Line productId | ItemCode | Matched imported product. |
Line quantity | QuantityOrdered | Ordered quantity. |
Line subtotalValue | Amount | Purchase-line amount. |
Line expectedDeliveryDate | DateExpected | Expected line delivery date. |
Receipt remoteId | PurchaseOrderNumber + _ + ItemCode | Same source pair as the purchase line. |
Receipt buyOrderLineId | Same purchase-number and item-code pair | Resolves to the imported purchase line. |
Receipt quantity | QuantityReceived | Current received quantity, not a separate receipt for each increase. |
Receipt occurred | ReceivedDate | Receipt 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.