Skip to content

Pet Food Wholesale Workflows: Route Minimum-Order and Freight Exceptions

Under-minimum and free-freight requests from independent stores go to the person with authority, and the approved terms stay attached to the NetSuite order.

Author
Ignacio Malpartida · GTM Engineer
Published
Read time
5 min read
Pet Food Wholesale Workflows: Route Minimum-Order and Freight Exceptions
APP TIPS

The operating decision

Use a pet-food wholesale workflow to check retailer minimums, freight conditions, and approved exceptions before creating or releasing an order. Keep requested quantities and approved terms explicit, including the recipe and bag-size mix. A salesperson’s promise should become an operational commitment only through the authorized decision path.

Explore the complete pet food and treats integration and automation hub for the systems and processes around this guide.

Summary card: Pet food wholesale workflow for minimum order exceptions

What this looks like in pet food and treats

An independent store requests several small quantities across recipes and asks for free freight. The total bag count meets one informal rule but not the customer’s actual case or value threshold. The workflow should evaluate the applicable agreement and route any exception before operations receives a conflicting instruction.

Records, ownership, and update rules

RecordOwnerOperating rule
Retailer requestSalesCapture store, payer, recipe and bag-size lines, quantities, and requested delivery.
Commercial policyAccount ownerOwn the applicable minimum, freight basis, and allowed exception authority.
Exception approvalAuthorized reviewerRecord the accepted quantity, charge, scope, and expiry of the decision.
ERP resultOrder operationsLink the accepted order and release state to the approved request.
Record ownership diagram: Retailer request, Commercial policy, Exception approval
Define the record owner and the rule before enabling updates.

Work through the process

  1. 01
    Apply the right rule
    Identify the agreement for the retailer and destination. Minimum cases, order value, and freight weight are different bases; preserve the required units and evidence rather than applying a universal bag-count threshold.
  2. 02
    Gather the complete request
    Resolve product variants and shipping location before review. A changed bag size or delivery destination can affect the decision even when the number of lines remains the same.
  3. 03
    Authorize the exception
    Route under-minimum or special-freight requests to the designated owner. Store the exact approved terms so another team cannot interpret a general positive message as unlimited authorization.
  4. 04
    Verify before release
    Compare the final order with the approved scope. If quantities or terms change, obtain the required review and preserve the accepted destination reference after execution.
  5. 05
    Cut an approved order and check whether the freight decision reopens
    Take an under-minimum request that an authorized reviewer approved with free freight, and confirm the approval record in NetSuite names the basis it was judged on: case count, order value, or freight weight, together with the quantity and charge the reviewer accepted. Then, before release, reduce one recipe line so the order falls below the quantity that approval covers. The workflow should move the order back to awaiting decision and post a new Slack request, marking the earlier approval superseded. Attempt the release without answering that request. If the order releases with free freight applied, the approval reads only approved with no basis, or the old exception carries over to the smaller order, stop the rollout.
5-step operating sequence: Pet food wholesale workflow for minimum order exceptions
Follow the operating sequence; unresolved exceptions return to a responsible reviewer.

Handle the exceptions explicitly

Retailer reduces quantities

Re-evaluate the threshold before release rather than retaining the old approval.

Request includes an unknown bag size

Resolve product identity before calculating the commercial rule.

Free freight was already approved for another order

Do not reuse an order-specific exception without explicit authority.

What to verify before expanding

  • The approval records the actual minimum or freight basis reviewed.
  • A changed order cannot silently inherit an unrelated exception.
  • Reducing a retailer order below the approved threshold reopens the minimum-order or freight decision before release.
  • A free-freight exception approved for one order cannot authorize another request without explicit review of its scope.
Book a demo for pet food and treats integration and automation

Connect this process to the rest of your operation

Explore Stacksync workflows and scope the records and actions against your actual systems. Book a demo with a real retailer request example and the exception your team handles most often, for example retailer reduces quantities.

The shared architecture guide covers record matching, ownership, and recovery across systems.

Technical references

Book a demo for pet food and treats integration and automation

FAQ

Frequently asked questions

Will one minimum-order rule work for every retailer?
No, and you should not want it to. Minimums live in the retailer agreement, which is why the workflow reads the policy from the account rather than from a single constant. Before the pilot, put the basis and figure on every wholesale account; an account with no policy recorded should route to the account owner as an exception, not fall back to a default. That gap list is often the first useful output of the project.
Where does the approved exception live after the order ships?
On the NetSuite order it was granted for, alongside the reviewer's name. It does not attach to the retailer account, so the next request from the same store starts with no exception in place. Slack holds the conversation, but the order record holds the decision; when finance audits freight exceptions later, nobody should need to search a channel. Reviewers see their past decisions by filtering orders on the approval field, not by memory.
What stops a rep's Slack message from becoming an order?
The workflow only creates or releases a NetSuite order from a request that has passed validation and, where needed, carries an approval recorded by a named reviewer. A reply in Slack along the lines of fine, ship it is captured as conversation, not as a decision. The reviewer confirms terms in the approval step itself, and the write to NetSuite is scoped to the sales order object with the approved values. Anything a rep types elsewhere stays outside the transaction.

About the author

Ignacio Malpartida
Ignacio Malpartida
GTM Engineer

Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale.

All posts by Ignacio Malpartida

About Stacksync

Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing.

Explore these integrations and topics

Keep reading

Related articles

All articles
App tips Pet Food Lot-Hold Workflows: Carry Approved Quality Decisions Into Order Operations 5 min read read
Data engineering HubSpot–NetSuite Sync for Pet Food Brands: Connect Independent Retailers and Reorder Status 5 min read read
App tips Pet Food and Treats EDI: Align Retailer Product Codes and Case Quantities 5 min read read
Coworkers laughing in front of a laptop in a casual office setting

You just read how it should work.
See it run on your own data.

Book a demo Get started