AlmondTill/G3N API

On this page

scheduleMarkdownPlan

mutation · in the family Pricing

What it does

Schedule a markdown plan — the price cuts will fire on their dates.

SCHEDULE a draft MarkdownPlan: (1) VALIDATE pure-reads — every step future · the scope resolves via the engine to ACTIVE products/variants × the plan's LF set → the InventoryItems THAT EXIST (ZERO resolved = VALIDATION/INVALID — a plan that moves nothing is an authoring error) · the ≤250-items/≤500-writes caps (VALIDATION/INVALID naming the figures) · per II: the schedule currency must EQUAL the plan currency (the law) · base₀ = the ACTIVE record covering step-1's startAt (none = VALIDATION/INVALID — a markdown MOVES an existing price) · the ladder (each PRIOR RESULT, half-away rounding) must stay > 0 · a forward splice check — ANY overlap refuses CONFLICT/PRICE_WINDOW_OVERLAP naming {II, blockers}, ALL-OR-NOTHING. (2) WRITE every future-dated SalePrice through the EXISTING per-record create (splice-gated, evented, plan/step-stamped; the FIRST window per II TRIMS the covering standing record). (3) FLIP draft→scheduled (OCC) stamping nextDueAt + resolvedInventoryItemIds. IDEMPOTENT-RESUME: a mid-flight fault refuses naming progress with the plan still draft — a re-run SKIPS its own already-written step-prefix and retries the flip. Requires the unrestricted capability + the record's CURRENT revision.

Careful

Scheduled markdowns change live prices when they fire.

Who may call it

Capability area: Pricing — Prices, price schedules, promotions, coupons and the money rules of selling.

Arguments

NameTypeRequiredNotes
inputScheduleMarkdownPlanInput ScheduleMarkdownPlanInput!yesNo further notes.

Returns

MarkdownPlan MarkdownPlan! — A MarkdownPlan — the markdown CADENCE: a product scope (the grammar VERBATIM — predicate + inclusions/exclusions + a Collection ref) + ≤ 8 ordered effective-dated steps (percent_off ppm-EXCLUSIVE · amount_off · to_fixed; startAt strictly increasing; the LAST step MAY carry endAt = the clearance-LAPSE arm, absent = the standing far-future window). the write rule: the schedule transition pre-computes the whole price LADDER per targeted InventoryItem (base₀ = the record covering step-1's startAt, then each PRIOR RESULT — half-away rounding, every result > 0) and WRITES EVERY future-dated SalePrice up-front through the existing per-record create (splice-gated, evented, plan/step-stamped; the FIRST window per II TRIMS the covering standing record; caps: ≤ 250 items · ≤ 500 writes). The prices then move by dated-window resolution ALONE — the scheduler fires ONLY the plan's own status flips (scheduled→active at the first step's moment · active→completed after the last; a down sweeper delays ZERO price moves — the flips are observability). The live splice law PROTECTS the cadence (an external overlapping write refuses CONFLICT/PRICE_WINDOW_OVERLAP naming the plan's records). Cancel dooms the not-yet-effective plan-stamped records ONLY (effective windows are permanent price history; the step-1 trim is NOT restored). A markdown MOVES the step-1 base — promotions/loyalty/employee compose on top UNCHANGED. Update is DRAFT-only (amend-after-schedule = cancel + author anew). At most 32 OPEN (draft+scheduled+active) per org group. Org participation is the canned-pool selection (≤ 32; ABSENT = every org); logicalFacilityIds (≤ 32) RESTRICTS within the selected orgs' facilities (ABSENT = all of them). NOT searchable (the document non-joiner stance — this born-paginated list is the discovery read); NO UNIQ marker.

Example request

mutation ExampleScheduleMarkdownPlan($input: ScheduleMarkdownPlanInput!) {
  scheduleMarkdownPlan(input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    organizationIds
    logicalFacilityIds
    currency
    nextDueAt
    resolvedInventoryItemIds
  }
}

Variables:

{
  "input": {
    "planId": "01900000-0000-7000-8000-744bf63f0000",
    "expectedRevision": "01900000-0000-7000-8000-e02b2e6c0000",
    "reason": "Correcting a miscount."
  }
}

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

Example response

{
  "data": {
    "scheduleMarkdownPlan": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "MD-EXMP-0000-000F",
      "type": "MarkdownPlan",
      "caption": "Blue jeans",
      "status": "draft",
      "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",
      "organizationIds": [
        "01900000-0000-7000-8000-60e064dc0000"
      ],
      "logicalFacilityIds": [
        "01900000-0000-7000-8000-2c5783bd0000"
      ],
      "currency": "USD",
      "nextDueAt": "2027-01-31T00:00:00.000Z",
      "resolvedInventoryItemIds": [
        "01900000-0000-7000-8000-0600d5020000"
      ]
    }
  },
  "extensions": {
    "at": {
      "callId": "01EXAMPLE-CALL-ID",
      "version": {
        "requested": {
          "name": "genesis",
          "number": 0
        },
        "serviced": {
          "name": "genesis",
          "number": 0
        }
      }
    }
  }
}

Errors this call can answer

Used in