Key takeaways
- Sample MOQ and production MOQ are different numbers, and a supplier who quotes them as one is quoting from a template.
- On an OEM project the mould already exists and stays with the factory.
- A certificate is a scope document disguised as a badge.
Most pet product sourcing projects that go wrong do not go wrong on price. They go wrong on four questions nobody put in writing: what the real production MOQ is, who owns the tool, what the certificate actually covers, and who controls the app. All four are cheap to settle at the quotation stage and painful to discover after the deposit — or worse, after the first container lands. Here is the checklist, question by question.
First question: what is the real production MOQ?
Sample MOQ and production MOQ are different numbers, and a supplier who quotes them as one is quoting from a template. A factory may happily sell you five sample units while the true production minimum, driven by tooling set-up or minimum material buys, sits far higher. Pin down three specifics: the MOQ for the first production order, whether that changes with a custom colourway, and whether a mixed container carries a per-SKU minimum. Precise answers mean the quote came from a production plan. Vague answers mean the negotiation has not started yet.
For reference, our own tiers run from 50-100 units for standard wholesale items, 1,000 units over 15-25 days for OEM, and 3,000 units over 30-45 days for ODM.
Second: who owns the tool?
On an OEM project the mould already exists and stays with the factory. On an ODM project with new tooling, ownership is the whole game — it decides what happens when you want to change suppliers, renegotiate, or simply keep production alive if a relationship sours. Four clauses belong in the contract before any tooling payment: that the buyer owns the mould, how the cost is amortised or paid up front, the right to transfer the tool to another factory, and who funds maintenance and refurbishment as it wears. Skip the transfer clause and you can pay for a mould twice: once to build it, once for the freedom to leave with it.
Third: what does the certificate actually cover?
A certificate is a scope document disguised as a badge. CE, FCC, RoHS and REACH paperwork attaches to a specific model, factory line and date; food-contact compliance adds another layer wherever plastic meets kibble or water. The verification habit is simple and non-negotiable: get the certificate number, check it against the issuing body, and confirm the declaration names your exact configuration — including the power adapter, which audits notice first. Scope gaps surface most often late in a project, after a colourway change or a hurry-up SKU addition, which is exactly when nobody wants to hear about them.
Fourth: who controls the app and the cloud backend?
This is the most under-examined risk in connected pet products. If the supplier hosts the app and the backend, then a discontinued line, a changed cloud provider or a quiet shutdown lands on your customers — and a feeder whose app dies is a return nobody recovers. Four questions, all answered in writing: who owns the app and backend; can the app be white-labelled and who controls updates; is there a local fallback mode when the cloud is unavailable; and what contractual commitment covers backend availability. On programmes like the 8L OEM camera feeder, buyers control the white-labelling and app naming directly, which is the arrangement worth asking for.
Then packaging, and finally the sample that decides it
Packaging is its own small project: barcode, country-of-origin marking, multilingual copy, handling icons and regional compliance text. Decide early whether the supplier designs the artwork or you supply it, and who owns the files either way — late artwork is a classic reason a production schedule slips. Then treat the production sample as evidence rather than ceremony. Measure the actual hopper or basin capacity instead of trusting the stated figure. Run the app through setup, reconnection and a firmware update. Operate the unit continuously long enough to observe heat and noise. And test with the kibble, litter or water type your market actually uses, because a unit that behaves in a showroom can still fail on local consumables. The 6L timed feeder's documented specification is a decent reference for what a production spec sheet should look like.
The four questions, in one paragraph
Ask all four before money moves. What is the real production MOQ? Who owns the tooling, and can it leave? What exactly does each certificate cover? Who controls the app when the relationship ends? Written answers to these map directly onto the exposures that matter: budget, leverage, market access and product lifespan. They cost one afternoon of emails at quotation stage and they are far more expensive to obtain retroactively. The PetAI Tech Global feeder line runs $25.90 to $76.90 wholesale with a 12-month warranty, and every one of these questions gets a written answer as standard.
Frequently asked questions
What MOQ applies to OEM and ODM pet product projects?
Standard catalogue orders start at 50-100 units. OEM private label on existing tooling starts at 1,000 units with 15-25 working days of production, and ODM projects with new tooling start at 3,000 units over 30-45 days including tooling.
Who owns the mould on an ODM project?
The buyer can own it, but only if the contract says so before tooling payment: who owns the mould, how the cost is amortised, whether it can be transferred to another factory, and who funds maintenance. Without a transfer clause, changing suppliers means paying for a second tool.
What should a certificate cover before I place a deposit?
A specific model, factory line and date, not a brand. Get the certificate number, check it with the issuing body, and confirm the declaration names your exact configuration, including the power adapter. Food-contact compliance is a separate file wherever plastic meets kibble or water.
Get the four answers in writing with your quotation: request a quote.
