BlogBuying and receiving4 min read

Vendor requirements: allowed vendors, SKUs on POs, and requested dates

Set the vendor's standing requirements once, then put the destination and delivery request where they belong on each purchase.

The OrderPilot team·

Viewed from overhead, Chip sits on a broad upholstery bench arranging blank material cards in morning sunlight.

One maker wants the SKU on every line. Another's order desk works from the item description and keeps misreading the store's identifier. A third needs a requested delivery date before it can plan the shipment. Vendors are particular; the details should not depend on which buyer remembers which conversation.

OrderPilot keeps vendor contacts, minimums, and SKU-printing choices with the vendor setup, and controls which vendors a product template can use. The individual PO then carries its destination, requested date, and delivery instructions. That division keeps standing requirements separate from the details of this purchase.

Keep the vendor identity and contact usable

Vendor names can be brought in from Shopify's vendor list. Add and maintain the contact information the buying team needs, especially the address that should receive purchase emails. A sales rep's inbox and the vendor's order-entry inbox may serve different jobs. Review a name change deliberately. Shopify vendor matching uses names, with case and spacing normalized; a genuinely different name can appear as another vendor rather than automatically transferring the earlier vendor's settings and purchase history. Check the imported records and contacts before using the changed name on a new purchase.

If your team says supplier or manufacturer, the Vendor wording setting changes the term across OrderPilot's Admin screens. POS retains Vendor. The store-terminology guide explains that small adjustment without confusing a change of label with a change of company.

Allow the vendors that can supply the template

A template can be associated with more than one vendor, or set to offer all vendors where that is the intended buying arrangement. Use the narrower list when a piece has a defined source. Use a broader choice only when the buyer can make a meaningful selection among suppliers. Two vendors appearing in a picker does not establish that their furniture is interchangeable. Check the specification, finish names, costs, and production arrangements before moving a purchase between makers. A familiar silhouette can hide a different seat depth, and seat depth has a habit of being noticed once someone sits down.

Keep that sourcing decision consistent with the customer agreement. If a vendor change alters something the customer was promised, resolve the customer-facing change too. The purchasing pillar explains how the sold specification remains the starting point.

Decide whether the SKU helps this vendor

The SKU-printing choice is set per vendor. Review the actual PO PDF with the vendor's requirements in mind. If the identifier is useful, it should be the correct one; if the vendor does not want it printed, the description and configuration must still identify the purchase clearly.

Say a sample sofa's frame code is MAD-90. Printing that code identifies the frame in this illustrative example, but it does not replace the fabric, arm, depth, or leg choices. A short identifier and a complete specification do different jobs.

Do not assume the SKU setting creates a separate vendor-specific identifier automatically. Review the data the line carries and the output the vendor receives. The furniture PO checklist helps separate the useful identifying fields from internal notes.

Put the purchase's dates and instructions on the PO

The requested delivery date and delivery instructions belong with the particular purchase. A warehouse dock appointment, customer-address restriction, or receiving contact can differ from one PO to the next, even when the vendor stays the same. Name the milestone clearly when discussing the date with the vendor. A requested delivery date is not its confirmed ship date. The acknowledgment should resolve what the vendor expects to do and when. Record any accepted change in the PO conversation so the team does not keep quoting the original request.

For minimums, use the quantity-and-value guide. Record the requirement and whether it is enforced, then review the shortfall before sending. Shipping instructions should not be used as a hiding place for a minimum the app can check directly.

Give the rep a short setup sheet

Use this sheet when opening or reviewing a vendor account:

Item to settleAnswer to keep
Vendor identityRecognized name and any name-change explanation
PO contactOrder-entry email and backup contact
Permitted productsTemplates and configurations the vendor supplies
IdentifiersWhether SKUs should print and which codes the desk uses
MinimumsQuantity, goods value, and any separate small-order arrangement
DatesMeaning of requested and acknowledged timing
ShippingDefault arrangements and details that vary by purchase
OwnershipStaff member responsible for keeping the setup current

Keep permissions aligned with that ownership. Buyers need dependable settings; they do not need every exception to become an unreviewed permanent change. Finish by reviewing a sample document with the PO checklist, so the written setup produces the purchase the vendor expects.

Give your team the tools they deserve

See what changes when every custom order lives in one place, from the showroom floor to your customer’s front door.