Order Lookup

outline when teamwork commerce is your order source, the returns portal is built from the teamwork sales order rather than from your online store the customer enters their order number and email as normal, and refundid asks teamwork for that order in the background how the order is found the customer's order number is matched against the teamwork sales order number if your order numbers carry a fixed prefix online (for example a web prefix) it is applied automatically, and a leading # is stripped, so the customer can enter the number in whichever form appears on their confirmation email the email the customer entered must match the email on the teamwork order if it doesn't or if the order number matches more than one teamwork order no order is returned and the customer is shown the standard "order not found" message this is deliberately strict rather than guess between similar orders, the lookup fails and tells the customer nothing about the order it stops one customer's details being shown to another what is pulled through for each item on the order, refundid reads title, variant (for example colour and size), sku and barcode unit price and quantity, with any line discount converted to a per unit amount so return values and fees calculate correctly on partial returns product categories your department, class and sub class values come through as categories, so they can be used in flows docid\ hh zbvcggpkocri2oam71 conditions product imagery, taken from the digital assets held against the product in teamwork where a product has several images, the thumbnail image is preferred if no image is available a neutral placeholder is shown instead of a broken image at the order level, refundid reads purchase date and fulfilment (shipped) date the delivery address outbound tracking number and carrier, taken from the shipping records on the order the payment method used, and whether a gift card was part of the payment so gift card orders can be treated differently in your resolutions and flows items that can't be returned items are returned to the portal with a returnable quantity of zero, and a reason shown to the customer, when they are cancelled or rejected on the teamwork order marked as a final sale item order metafields the teamwork order number is passed through as an order metafield, so it can be used in flows conditions with the order metafield condition additional metafields can be added on request a common use is to flag whether a particular product or service was purchased on the original order, so returns of those orders can follow a different flow