Before you compare Vendit data

Confirm API access and the stock, sales, purchase and export-office selections through the Vendit setup guide. Identify the entity and direction before comparing fields. A Vendit reference resolves to a matched Optiply record where a relationship is required.

Steps to compare Vendit data

  1. Choose the entity and direction you need to check.
  2. Find the field in the matching table below.
  3. Compare source and destination using that entity's identity.
  4. Apply the office, availability and purchase-status conditions.
  5. For an export, check Vendit's pre-purchase list before the final purchase order.

Fields in Vendit imports and exports

Products: Vendit to Optiply

Optiply fieldVendit fieldMeaning or condition
remoteIdproductIdStable product identity.
nameproductDescriptionProduct description.
skuCodeproductNumberProduct SKU.
eanCodeproductSearchCodeSearch code used in the EAN field.
articleCodeproductGuidProduct GUID.
priceFirst usable salesPrices.items.salesPriceExPrice excluding VAT, rounded to two decimals. Missing usable prices become 0.
unlimitedStockInverse of useStockStock tracking means unlimitedStock is false.
stockLevelProduct availableStock, then stock-change totalsSee the stock rules below.
statusavailabilityStatusIdValues 1 and 4 enable the product. Other values disable it.
notBeingBoughtDisabled status and positive stockTrue only when both conditions apply.

Product stock provides the initial total across its available offices. When stock-change data exists, selected-office totals replace that baseline. Stock changes are retained per product and office, then summed. A partial change does not replace the entire total with that one change. Products without a matching selected-office total receive stock 0 in that replacement path.

Suppliers and supplier products: Vendit to Optiply

Entity and Optiply fieldVendit fieldMeaning or condition
Supplier remoteIdsupplierIdSource supplier identity.
Supplier namesupplierNameSupplier name.
Supplier emailssupplierEmailSupplier contact addresses.
Supplier deliveryTimedeliveryDaysSupplier lead time.
Supplier product remoteIdproductSupplierIdSupplier-product identity.
Supplier product namesupplierProductNumberSupplier product number.
Supplier product supplierIdsupplierIdMatched Optiply supplier.
Supplier product productIdproductIdMatched Optiply product.
Supplier product pricepurchasePriceExPurchase price excluding VAT.
Supplier product preferredpreferredDefaultSupplierPreferred supplier indication.
Supplier product deliveryTimeexpectedArrivalDatetimeSubject to numeric lead-time conversion, not copied as an arrival date.
Supplier product minimumPurchaseQuantityminOrderQuantityRounded whole quantity, minimum 1.
Supplier product statusavailabilityStatusIdValues 1 and 4 enable it. Other values disable it.

Supplier-product lead time is limited to 365 after numeric conversion. Values of 1 or less, and unusable values, are left unset. Check the actual lead-time result rather than interpreting the source field name as a delivery-date promise.

Sales orders and lines: Vendit to Optiply

Entity and Optiply fieldVendit fieldMeaning or condition
Order remoteIdsaleHeaderIdTransaction identity.
Order totalValuetotalPriceExVatTotal excluding VAT.
Order placedtransactionDatetimeTransaction date.
Line remoteIdsaleDetailIdSource line identity.
Line sellOrderIdsaleHeaderIdMatched imported transaction.
Line productIdproductIdMatched imported product.
Line quantityproductQuantitySold quantity.
Line subtotalValueproductTotalSalesPriceExLine total excluding VAT.

The sales-office selection filters transactions. Existing sales orders and lines are not updated. Lines must belong to newly imported sales orders. New lines added to an existing order are not imported through that route. Repeated lines for one order and product combine quantity but retain the first subtotal. Lines with product ID -1 are excluded.

Purchase exports: Optiply to Vendit

Optiply valueVendit fieldMeaning or condition
Buy-order IDoptiplyId, orderReferenceIdentifies the originating Optiply order.
Source product referenceproductIdVendit product identity, not an Optiply database ID.
Line quantityamountQuantity for the pre-purchase line.
Purchase export datecreationDatetimeDate supplied for the exported order.
Calculated unit pricepurchasePriceExPositive subtotal divided by positive quantity, otherwise supplier-product purchase price, otherwise omitted.
Source supplier referencetargetSupplierIdExport supplier.
Configured export officeofficeIdIncluded when an export office is configured.

Each order line is sent separately to the pre-purchase list. Convert the lines into a final purchase order in Vendit. A line already present with the same order reference and product is skipped. This check covers the pre-purchase list and open purchase orders, not fully delivered orders. Do not treat it as universal duplicate protection.

A missing usable unit price is omitted, not replaced with 0. Missing product identity or quantity prevents that line from being sent.

Purchase orders: Vendit to Optiply

Optiply fieldVendit fieldMeaning or condition
remoteIdpurchaseOrderNumberPurchase identity.
supplierIdsupplierIdMatched Optiply supplier.
placedorderDatetimeHistory also accepts orderDateTime. If absent, it uses the latest delivery timestamp.
totalValueOpen: sum of amount × purchasePriceEx. History: sum of amountDelivered × purchasePriceEx.Totals are combined when the purchase occurs in both sources.
expectedDeliveryDateOpen: earliest line expectedDeliveryDate.Historical headers do not supply this field.
completedLatest received timestamp across known receiptsSet only when received quantities cover every known ordered line.
Export linkoptiplyIdLinks an exported Optiply purchase. orderReference is not used as the import-link substitute.

Purchases without a usable placed date are excluded. Ad-hoc history purchases are excluded. If one export link points to several source purchases, it is cleared rather than used to merge unrelated purchases.

Purchase lines: Vendit to Optiply

Optiply fieldVendit fieldMeaning or condition
remoteIdpurchaseOrderNumber + _ + productIdPurchase-product pair.
buyOrderIdpurchaseOrderNumberMatched imported purchase.
productIdproductIdMatched imported product.
quantityOpen: amount. History: amountOrdered.Historical values replace open values for the same pair.
subtotalValueOpen: amount × purchasePriceEx. History: amountOrdered × imported product price.Uses different price inputs for open and historical lines.
expectedDeliveryDateOpen: expectedDeliveryDate. History: deliveryDatetime.Date for the corresponding source.

The imported product price is the product sales price described above, not the supplier-product purchase price. Keep that distinction when comparing historical purchase totals.

Receipts: Vendit to Optiply

Optiply fieldVendit fieldMeaning or condition
remoteIdproductPurchaseHeaderId + _ + productIdDelivery-header and product pair.
buyOrderLineIdpurchaseOrderNumber + _ + productIdResolves to the imported purchase line.
quantityamountDeliveredDelivered quantity, rounded to a whole number.
occurreddeliveryDatetimeDelivery timestamp.

Receipts come from purchase history. They need positive quantities and matched purchase lines. Existing receipt updates compare quantity, not every field.

What you see when comparing Vendit data worked

You can match each record by its entity-specific identity and explain the office selection. You can distinguish open and historical purchase prices. For exports, you can locate pre-purchase lines before converting them into a final purchase order.

Limits of comparing Vendit data

The stock baseline and stock-change replacement use different office handling. Historical purchases use imported product prices. Existing sales changes are not synchronized through the new-order route. Existing-line export checks do not cover fully delivered orders. A matching field does not confirm that the latest transfer completed.

If comparing Vendit data did not work

Check the office selection and availability status first. For missing lines, check the matched product, supplier and parent purchase. For missing exports, check the pre-purchase list and open purchases before requesting a retry. Give Support the direction, field and comparison time through the setup guide. Do not resend a whole order to repair one failed line.