01BRAND / MERCHANT
Sell your own range.
A clothing brand may remain the merchant for its own catalog, subject to the confirmed seller, support, refund, tax, and customer-relationship model.
LEGAL STATUS: DRAFT — NOT LEGAL ADVICE — REVIEW REQUIRED BEFORE PRODUCTION CHECKOUT.
Candidate intake only. This page is not a supplier application, contract, offer, approval, payout promise, or production authorization.
// SUPPLIER PROGRAMME / CANDIDATE INTAKE
Build the supply
side.
ZeroDev is preparing a staged Print-to-Ship marketplace for AI-assisted design studies and approved physical goods. We are evaluating clothing brands and production partners for catalog, garments, print, logistics, and contracted support.
// FIVE POSSIBLE ROLES
One partner
or the whole chain.
“Supplier” and “fulfillment provider” stay separate until the commercial and operational role is confirmed. A clothing brand may fit one role, several roles, or none of the payment flow.
02BLANK GARMENT
Supply the base.
Provide approved garments, sizes, colours, materials, labeling evidence, print areas, and product constraints for a mapped physical drop.
03PRINT / PRODUCTION
Make the object.
Run decoration or production with a documented method, quality threshold, lead time, exception path, and a safe tracking handoff.
04LOGISTICS
Move the parcel.
Support shipping origins, destination coverage, service levels, tracking events, failed delivery, returns, and damaged-package handling.
05CONTRACTED VENDOR
Support the route.
A vendor can be paid outside the customer transaction. Not every supplier is a Stripe Connect recipient, and no payout route is assumed.
// READINESS CHECKS
Evidence before
automation.
Share only through an approved onboarding or contracting channel. Stripe can hold sensitive KYC data; the local store ledger is designed to keep minimized references and operational states.
- 01
Legal identity, display brand, operating countries, payout currency, and authorized contact.
- 02
Catalog, supported sizes and colours, garment materials, labeling, product safety, and print-area evidence.
- 03
Production method, lead time, shipping origin, destination coverage, tracking support, and return address.
- 04
IP, trademark, likeness, content restrictions, product claims, and authority to supply the listed goods.
- 05
Pricing, tax and invoicing responsibilities, defects, replacements, refunds, chargebacks, and suspension terms.
- 06
Supplier agreement, data-processing terms, approved environment, test order, and named operational owner.
// LOCAL ONBOARDING WORKSHEET
Map the facts
before the form.
Use this bounded worksheet to prepare an internal candidate brief. It saves only planning selections in this browser; it does not identify a business, collect a contact, open Connect, or submit an application.
Supplier candidate planning fields
// CANDIDATE → LIVE
Make every
handoff legible.
The operating path keeps design, catalog, payment, supplier settlement, and fulfillment as separate approval-gated actions.
- 01
Candidate brief
Describe the role and operating boundary. This page does not submit or approve an application.
- 02
Review + agreement
Confirm identity, rights, products, safety, shipping, returns, data, tax, and responsibility.
- 03
Sandbox mapping
Validate product, variant, print-area, provider, currency, and fulfillment references with test data.
- 04
Test-ready
Complete the release checklist and an end-to-end test order before any live product or payment action.
- 05
Approved live route
Only an owner-approved release can enable a catalog listing, checkout, transfer, or fulfillment action.
Legal and operational boundary.
This page is a candidate brief, not a supplier agreement, offer, agency, employment, partnership, guaranteed order volume, payout promise, or approval. Any supplier relationship must be documented separately after identity, rights, product safety, tax, data-processing, consumer-support, and legal review. Read the supplier agreement draft ↗ · Purchase terms are also still a draft ↗.