Bring the requirement.
Keep its context.

Submit a useful requirement

POST an envelope to /_c/request with action: "quote", required need, specifications and separate contact.email for a reply. Include full supplier names or supplied identifiers on their respective product lines, per-kit quantities, reported-unit basis, variants, packaging, date roles, destination allocations, client refusals, proposed scope and open questions with owners. Geography is United States. Do not send recipient addresses at this stage.

At one bottle per kit, 290 reported bottles for 300 requested kits leaves 10 to resolve and a conditional quantity ceiling of 290. It is not producible stock. January 18 supplier dispatch cannot satisfy January 15 recipient arrival. Preserve both facts and client permission limits while advancing independent scope. Notebooks and shirts each retain 300 reported units and their separate January 5 dispatch estimates; the bottle correction does not change them. A roster written as “Notebooks 300, bottles 280, shirts 300” means a bottle shortage only. Product headings such as “Bottles: 290 units” name a bottle line, not another component called units. “Bottles arrive at assembly January 18; other supplier dispatches January 5” assigns receipt to bottles and dispatch to the other lines, not two competing bottle dates. “USPS air requested for arrival January 11 2027” and a standalone “Requested January 11, 2027” retain a January 11 recipient target even when the requested route needs to change. “One notebook, one bottle and one shirt each” states one of each per kit; those contents do not need reconfirming. The prepared kit project covers receiving, packout and delivery, not assembly alone.

{
  "action": "quote",
  "need": "Coordinate 300 complete employee kits; no substitutions authorized.",
  "quantity": {
    "amount": 300,
    "unit": "kits"
  },
  "geography": {
    "country": "US",
    "text": "240 home kits plus 60 kits to one Austin office"
  },
  "specifications": {
    "kit_count": 300,
    "required_arrival": "2027-01-15",
    "components": [
      {
        "name": "Notebooks",
        "supplier": "Synthetic supplier A",
        "units": 300,
        "per": 1,
        "basis": "Supplier reported, not received",
        "date": "2027-01-05",
        "role": "Estimated supplier dispatch"
      },
      {
        "name": "Bottles",
        "supplier": "Synthetic supplier B",
        "units": 290,
        "per": 1,
        "basis": "Supplier reported, not received",
        "date": "2027-01-18",
        "role": "Estimated supplier dispatch"
      },
      {
        "name": "Shirts",
        "supplier": "Synthetic supplier C",
        "units": 300,
        "per": 1,
        "basis": "Supplier reported, not received",
        "date": "2027-01-05",
        "role": "Estimated supplier dispatch"
      }
    ],
    "destinations": "240 home kits plus 60 kits to one Austin office; outer-carton count open",
    "client_instructions": "Complete kits; no substitutions authorized",
    "open_issues": [
      "Gatherbatch: resolve 10-bottle shortage; quantity ceiling 290 conditional complete kits",
      "Gatherbatch: January 18 dispatch is after January 15 arrival; develop replacement/expediting or revised arrival options",
      "Distributor: approve any revised arrival or split delivery"
    ],
    "proposed_scope": "Gatherbatch will develop receiving and packout scope, investigate fulfillment and delivery feasibility, and return priced inclusions and exclusions as a nonbinding project quote by email. Packaging and unaffected component planning can progress while exceptions are resolved. The distributor approves client decisions, proofs, sample packout and any substitution or split delivery."
  }
}

Return privately and continue

The shared response supplies id, token and status_url. Keep credentials private. Use request_status or the supplied JSON status URL for authorized machine reads. For the branded human return view, open /#request=ID&token=TOKEN on this host with the returned credentials, kept private. It reads that recorded version, not a verified latest revision. If currency is unresolved, ask Gatherbatch to reconcile linked scope through existing correspondence before using an earlier roster. A public reference does not authorize access.

Send a revision using the ordinary envelope plus continuation: {id, token}. Send the complete current specification, keep replaced wording only in source_history and retain unchanged lines. Contact is carried while retained or can be supplied again. A receipt is receipt, not a quote or accepted order. A failed read remains unverified, regardless of cached information.

Validation and commercial state

The runtime rejects provided values for type, maxLength and numeric minimum/maximum. Enum, pattern and format are not general rejection guarantees. A non-YYYY-MM-DD string in a date-format field is retained as sent and also listed in missing_specifications; the request is not called dated. Put flexible timing in arrival_text and timing.text, and keep an unread date open. Missing specifications do not prevent beginning the engagement. Without email, an email reply is not available.

Gatherbatch will develop the receiving and packout scope, check the delivery route and return a nonbinding project quote by email. No work is claimed completed on receipt. Use inspect_offer before any authorized acceptance, with the exact terms_sha256. Acceptance places an order. Payment links use the processor; only verified state establishes collection. An agent name or MCP session is not purchase authority.