AlmondTill/G3N API

On this page

handoverFulfillment

mutation · in the family Fulfillment

What it does

Hand a pickup fulfilment to the customer — the goods change hands.

Hand over a staged pickup Fulfillment: ONE transaction relieves the claimed lines through the sell-relief lane (release of the ecom reserve rides it; COGS stamps at the current WMA), stamps the ORDER line fulfilledQty rollups + both delivery vectors, and — when the order is also fully paid — completes it (system:fully_paid_and_delivered). The capture seam is DECLARED-dormant. Requires the unrestricted capability + the CURRENT revision (OCC).

Careful

The handover is the delivery moment — after it, returns are the lane back.

Who may call it

Capability area: Selling — Ringing sales, serving customers and issuing invoices.

Arguments

NameTypeRequiredNotes
idID ID!yesThe id of the record.
revisionID ID!yesThe revision id you read on the record; the change is refused if an edit landed in the meantime.
reasonStringnoNo further notes.

Returns

Fulfillment Fulfillment! — A Fulfillment — groups order lines fulfilled together by ONE method from ONE LF: pick → pack → ship-or-stage → deliver. Ship = delivered (the operator ruling — the ship call fires BOTH edges); delivery relieves stock through the sell-relief lane (release of the ecom reserve rides it), stamps the ORDER line fulfilledQty rollups, and recomputes both delivery vectors; the completion evaluator flips a paid-and-delivered order to completed. After pack the record IS the Packing-List node (packedAt + the immutable lines; the FF-… sysId is the document number). Carryout lines NEVER ride a Fulfillment (the paid-completion till lane); dropship + ship-from-other-store are the named /Transfer-composition deferrals.

Example request

mutation ExampleHandoverFulfillment($id: ID!, $revision: ID!, $reason: String) {
  handoverFulfillment(id: $id, revision: $revision, reason: $reason) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    orderId
    organizationId
    method
    carrierName
    trackingRef
    packedAt
  }
}

Variables:

{
  "id": "01900000-0000-7000-8000-37386ae00000",
  "revision": "01900000-0000-7000-8000-b7960e180000",
  "reason": "Correcting a miscount."
}

Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.

Example response

{
  "data": {
    "handoverFulfillment": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "FF-EXMP-0000-000F",
      "type": "Fulfillment",
      "caption": "Blue jeans",
      "status": "pending",
      "parentId": "01900000-0000-7000-8000-065235280000",
      "rootId": "01900000-0000-7000-8000-a093dd800000",
      "createdAt": "2027-01-31T00:00:00.000Z",
      "updatedAt": "2027-01-31T00:00:00.000Z",
      "revisionNum": 1,
      "revision": "01900000-0000-7000-8000-b7960e180000",
      "orderId": "01900000-0000-7000-8000-f6d8263a0000",
      "organizationId": "01900000-0000-7000-8000-44b781470000",
      "method": "ship",
      "carrierName": "Blue jeans",
      "trackingRef": "<tracking ref>",
      "packedAt": "2027-01-31T00:00:00.000Z"
    }
  },
  "extensions": {
    "at": {
      "callId": "01EXAMPLE-CALL-ID",
      "version": {
        "requested": {
          "name": "genesis",
          "number": 0
        },
        "serviced": {
          "name": "genesis",
          "number": 0
        }
      }
    }
  }
}

Errors this call can answer

Used in