Release VFD Feed Only When a Valid VFD Covers the Order

A VFD belongs to the order, not to the account. The agriculture hub gates Restricted Use Pesticides by an applicator credential held on the buyer's account. A VFD works differently. FDA's rule at 21 CFR 558.6 lists what the veterinarian puts on a VFD. That includes "The premises at which the animals specified in the VFD are located" and "The species and production class of animals to be fed the VFD feed". It also includes the drug, the approximate number of animals and an expiration date. So one hog operation can hold three VFDs at once, for different drugs, barns and dates. Each VFD feed line has to match one of them, not just the customer.

The rule tells the mill when it may fill. The same section states: "The distributor is permitted to fill a VFD only if the VFD contains all the information required in paragraph (b)(3) of this section." It permits distribution only of feed that "complies with the terms of the VFD". It also states that "The distributor must keep records of the receipt and distribution of all medicated animal feed containing a VFD drug for 2 years." Picture the order desk on a Monday. A VFD arrives by fax, the producer calls in a load, and someone ties the two together by hand before the truck is loaded.

Expiry and reorders break the standing order. The rule states that "A VFD feed or combination VFD feed must not be fed to animals after the expiration date on the VFD." Where the drug's approval sets no date, "the expiration date of the VFD must not exceed 6 months after the date of issuance". On refills it is just as direct: where the labeling does not specify them, "reorders (refills) are not permitted". A standing order that regenerates every week cannot carry the VFD feed line past the VFD's expiration date.

The VFD counts animals, not tons. FDA's Guidance for Industry #120 explains that "the VFD specifies the number of animals that will be fed and not the exact amount of feed that can be manufactured". It adds: "we expect that feed mills will only distribute VFD feeds in quantities that are commensurate with the approximate number of animals as specified by the veterinarian in the VFD". Say a VFD covers roughly 2,400 finishing hogs across two barns. Each load on the Tuesday route counts against it, and the producer calls to adjust as the pigs grow.

Bulk feed moves by the ton, on a route, into a bin. A bulk order is a ration, a tonnage, a bin and a route day. The tonnage comes from head count, the feeding program and the days to the next stop, capped by what the bin holds. Rations change as the animals grow. FDA's guidance says "It is acceptable to feed several nutritionally different rations under a single VFD so long as each of those rations is consistent with the VFD and the drug approval."

Dealers and farm stores are distributors too. The rule lets a mill ship VFD feed to another distributor "only if the originating distributor (consignor) first obtains a written (nonverbal) acknowledgment letter" from the receiving one. FDA's guidance describes a mill that "distributes retail stock under an acknowledgment letter to another VFD distributor such as a farm store." So the same bag of VFD feed meets a different gate depending on who is buying it: a letter for the dealer, a VFD for the producer.

The VFD sits on the account, and each order checks it. In Uncap Portal, producers and farm managers get real multi-user accounts with roles and permissions, and each buyer sees their assortment and pricing. A VFD record on the account, holding the veterinarian's copy and the fields your order desk checks today, is built during implementation, with the release rule on top. As built, a VFD feed line releases only when a complete VFD on file matches the client, the premises on the delivery address, the species and production class, the drug in the formula and an expiration date after the delivery date. When nothing matches, the line holds for your VFD coordinator. The storefront does not decide what is lawful; it holds what your team has not cleared.

Tons counted against the animals on the VFD. A running total of feed shipped under each VFD, compared against a ceiling your nutritionist sets from the approximate number of animals and the ration, is built during implementation. Routing an order that would cross the ceiling into a quote in Uncap Quotes is built during implementation, and Quotes sends exceptions to the right approver. Approved quotes turn straight into Shopify orders.

Standing orders sized to the herd and stopped at the VFD's edge. Portal keeps reorder lists and order history a click away. Standing order generation, sized from head count, the feeding program and bin capacity and set to the route day, is built during implementation. In that build, VFD feed lines repeat under the same VFD until its expiration date, in line with FDA's guidance on batches of feed "shipped under the VFD", and stop there. After that, a line continues only under a new VFD or a reorder that VFD authorizes. When the ration changes, the check runs again against the same VFD.

Dealers gated by acknowledgment letter, producers by VFD. Account types, so a distributor account needs a current acknowledgment letter on file and a producer account needs a matching VFD, are configured during implementation. Bagged feed, mineral and supplements sell by the bag and the pallet at each dealer's price. Portal sets budgets, approvals and limits per user, so a barn manager orders while the owner approves anything over a set amount.

The record you keep, attached to the order. Recording on each VFD feed line the VFD it was filled against is built during implementation. Bagged medicated feed carries a batch, and the ERP tracks medicated feed by batch. Batch-level availability, so the storefront only promises a quantity a single batch can fill and the order records which batch it ships from, is built during implementation on inventory synced through Uncap Connect. A bulk load can draw on more than one batch, so the bulk rule is set during scoping and the order records each batch in the load. FDA's guidance says it anticipates "storage as a PDF file will be a common method for the maintenance of these records by distributors and clients", so the VFD copy can travel with the order as a file. Retention and export are set with your regulatory team.

On the question of whether regulated feed needs a heavier platform. On Shopify, the VFD release rule is built during implementation from your VFD records and the customer, formula and price data your ERP already holds. The useful question is where it reads that data. Integration runs through an owned Uncap Connect app embedded in Shopify, or a managed iPaaS integration, and the route for your ERP is confirmed during scoping. The Connect page describes middleware as "a separate platform that sits between systems and has to be run and maintained on its own." Connect keeps pricing, inventory, customers and orders current on both sides in real time. It syncs customer-specific pricing, credit terms and tax rules, and the ERP stays the system of record. On the Connect route, there is no separate middleware platform to keep running.

Contract feed pricing, delivery and terms on one order. Uncap Quotes applies negotiated prices, tiers and volume breaks automatically. Quotes carry validity windows, which suits a booked price per ton. Portal lets a Shopify store sell services and rentals alongside standard ecommerce products, so delivery or a bin rental sits on the same order as the feed. NET terms, invoices and payments live in the portal.

Adjacent proof, labeled as adjacent. Uncap has not published a feed mill case study. The closest is Farmers Depot, an agriculture B2B catalog on Shopify. Its case study says "Every buyer logs in and sees their company's price, storewide." Its ERP integration runs through middleware that is monitored automatically, not Uncap Connect, and it does not show VFD gating.

VFD on file, matched per line. Client, premises, drug, species and production class and expiration checked against each VFD feed line before release, built during implementation.

Expiry stops on standing orders. VFD feed lines on standing orders stop at the VFD's expiration date and continue only under a new VFD or a reorder that VFD authorizes, built during implementation.

Tons against animals. A running total of feed shipped under each VFD, with over-ceiling orders routed to a quote for approval, built during implementation.

Standing orders by head count and bin. Deliveries sized from head count, ration and bin capacity, set to the route day, built during implementation.

Acknowledgment letters for dealer accounts. Distributor accounts buy VFD feed only with a current acknowledgment letter on file, configured during implementation.

VFD and batch on the order record. Each line records the VFD it was filled against and the batch it shipped from, built during implementation.

Caution statement on VFD products. The statement quoted in 21 CFR 558.6(a)(6) displayed on every VFD feed product page, configured during implementation.

Account pricing and delivery on one order. Negotiated prices and volume breaks through Uncap Quotes, with delivery, custom mixing and bin rental as line items.

ERP sync, Connect or managed iPaaS. Pricing, inventory, customers and orders kept current between Shopify and the ERP, through an owned Uncap Connect app embedded in Shopify, or a managed iPaaS integration.

The honest line between product and build. Account pricing, quote approvals, reorder lists, budgets and NET terms ship in Uncap Quotes and Uncap Portal. The VFD record, release rule, tonnage ceiling, standing order sizing, letter gating and the VFD and batch on each order line are built during implementation. The scope shows which is which before the build starts.

Your regulatory team owns the rules. Uncap does not interpret the VFD regulation for you. Your team decides what counts as a match, where the ceiling sits and who clears a held line. The build applies those decisions on every order and records what was checked.

Credentials you can check. Uncap is a Shopify Platinum Partner, on Shopify since 2013, with 380+ unified storefronts launched on Shopify.

Scoped before it is built. The Uncap Blueprint is a fixed-price, four-week plan written before any build starts, credited 1:1 toward implementation. It covers solution architecture, a data migration taxonomy, an ERP integration audit, UX and flow prototyping, total cost of ownership and a risk register, and ends with a fixed-cost implementation estimate. For a feed mill, that architecture work can cover the VFD record, the release rule and the ERP mapping behind them. You walk with everything you need to brief any agency or your in-house team.

This page sits under agriculture and farming ecommerce, which covers seasonality, negotiated grower pricing, credit and settlement, pre-season programs and account-level gating for Restricted Use Pesticides. This page goes one level down, into feed, where the gate is a VFD on each order rather than a credential on the account. If you also sell restricted crop chemicals, see crop protection and chemicals ecommerce; if your trucks also haul fertilizer by the ton, see fertilizer and soil amendments ecommerce. Field notes: livestock and animal health reorder programs and how farm supply distributors move ordering online. For the ERP side, see the Dynamics 365 Finance and Operations integration, the Epicor Eagle integration, or the full list of ERP integrations.

Bring two documents: a month of VFDs from your order desk with the loads shipped against each, and the route sheet for one delivery day with bin sizes and head counts. Between them they show how the VFD check, the tonnage ceiling and the standing order have to work.

Book a strategy session with Uncap, or start with a Blueprint if what you need first is the VFD rules and ERP mapping written down and costed.