Counsel-review workspace
One organized packet for customers, sellers, co-ops, drivers, payments, delivery, content, and food-safety review. Every document is deliberately non-effective until qualified reviewers approve and publish an exact version.
These drafts cannot authorize selling, delivery, payment, data processing, or production launch. FOODERCE must publish an approved database version before collecting acceptance.
2 drafts
Customer, account, marketplace, and privacy foundations.
Describes the information FOODERCE expects to collect and the controls that must be approved before real-person data is processed.
Audience: Customers, applicants, sellers, drivers, and site visitors
Review draftSets the proposed rules for using FOODERCE while keeping seller, driver, payment, and jurisdiction-specific obligations in separate agreements.
Audience: All FOODERCE account holders and visitors
Review draft7 drafts
Baseline seller terms plus business-model-specific obligations.
The proposed baseline agreement every transacting seller must accept before listing products, receiving orders, or receiving payouts.
Audience: Farms, cottage-food operators, restaurants, makers, co-ops, and other participating sellers
Review draftAdds jurisdiction, product, labeling, preparation-location, direct-sale, and delivery restrictions for sellers relying on a cottage-food exemption.
Audience: Home- or farm-kitchen sellers operating under a cottage-food or similar exemption
Review draftAdds commodity-specific authority, source, handling, claims, traceability, and recall duties for farm and producer listings.
Audience: Farms, ranches, apiaries, orchards, dairies, egg, meat, and other primary producers
Review draftAdds facility, menu, food-code, shared-kitchen, preparation, allergen, and handoff requirements for prepared-food sellers.
Audience: Restaurants, bakeries, butchers, caterers, food establishments, shared kitchens, and their authorized users
Review draftDetermines whether the organization or each member is the legal seller and prevents authority, payout, catalogue, and liability ambiguity.
Audience: Cooperatives, farmers-market operators, food hubs, buying clubs, and multi-vendor organizations
Review draftExplains the difference between private application evidence, public profile information, processor data, statutory marketplace verification, and audit retention.
Audience: Prospective and active sellers and their representatives
Review draftGives FOODERCE limited content rights while keeping sellers responsible for review and preventing unapproved AI publishing or unsupported claims.
Audience: Sellers using FOODERCE's storefront, menu, image, or copy tools
Review draft5 drafts
Rules requiring operating, finance, insurance, and legal decisions.
Defines the proposed delivery relationship, safety duties, compensation disclosures, privacy limits, and evidence rules without deciding worker classification or insurance.
Audience: Approved shoppers and delivery participants
Review draftA decision framework for failed, changed, cancelled, unsafe, or disputed transactions; amounts and deadlines remain subject to approval.
Audience: Customers, sellers, drivers, and support reviewers
Review draftAssigns location, timing, custody, address privacy, proof, cancellation, and incident responsibilities for each fulfillment method.
Audience: Sellers enabling customer pickup, seller delivery, or FOODERCE-assisted delivery
Review draftNames every financial category that needs an approved amount, owner, timing, and failure rule before real transactions are enabled.
Audience: Customers, sellers, co-ops, drivers, and finance/support operators
Review draftA proposed stop-sale and response procedure for illness, allergen, contamination, tampering, mislabeling, temperature, and regulator notices.
Audience: Sellers, compliance reviewers, support, delivery operators, and incident owners
Review draftBusiness owners set the commercial choices; qualified marketplace, food, privacy, tax, employment, insurance, and payments reviewers approve the relevant language; engineering then stores the approved body as a new immutable version and requires role-appropriate acceptance. Draft edits never silently modify an accepted version.