commerce_creation_get

Prepare a complete X00004 product draft and return its creation revision. This read creates no product, uploads no image and reserves no slug.

Connected source: Only X00004 is exposed here; legacy shops and ticket events in the owner module are not connected. The source registry has 153 operations while the older recorded runtime has 145. Follow the common shop connection.

Existing drafts without these fields retain their prior contract.

Complete draft input

Require channelCode, pAppCode:X00004 and draft. No requestId, expectedRevision or dryRun is accepted by this preparation read. Supply completed commerce_image_upload task IDs bound to the same operator/connection/credential version, installation, purpose and configured storage.

Existing association IDs and option keys accept 1–160 ASCII letters, digits, underscores or hyphens. Image task IDs instead use the 8–80-character request-ID rule. IDs must come from observed records; titles and numeric row IDs are not replacements.

Base and non-null original prices follow the existing product price rules: KRW 100–9,999,999,990 in multiples of 10; USD 1.00–9,999,999.00 in 0.01 steps. Base price may equal but not exceed a supplied original price. There is no currency override or conversion. These are source configuration constraints, not a completed checkout or billing calculation.

Options and initial stock

For options.kind:single, supply quantity (integer 0–99,999,999) and optional sku (default empty). The source builds one Default/standard option and one ACTIVE tracked-inventory variant with zero additional price. Product saleStatus is separate from that variant status.

For options.kind:combined, supply 1–3 groups and 1–300 variants. Each group has a unique key, a trimmed title of 1–25 units and 1–300 values with globally unique keys and trimmed names of 1–50 units. The product of the group value counts must not exceed 300. Each variant supplies quantity, explicit ACTIVE/DISCONTINUED saleStatus and values selecting exactly one key per group in group order. Combinations must be distinct and every declared value must be used; the schema does not require every possible combination.

Both forms accept sku up to 100 ASCII letters, digits or hyphens, including empty. Combined variants additionally accept a signed decimal-string additionalPrice, default "0". Its magnitude and base-plus-additional total must stay within the currency maximum; the total may be zero, and KRW adjustments use multiples of 10. Every new variant tracks inventory. No per-variant image, access controls or scheduled sale period is exposed. Initial buyer input and add-ons are part of the complete creation draft; omitting them retains the earlier empty arrays. Common connection for these initial options is separately scoped below.

Preparation output and next step

COMMERCE_CREATION_READY includes revision, the source-shaped request, resolved images and dependency records, with writesPerformed:false. The workflow reads the draft's image/dependency snapshot twice and checks current context. Shipping/category/label/badge records must belong to the existing store and not be purged/archived.

Copy revision into commerce_create.expectedRevision and submit the same complete draft. This is not creationRevision and not a revision from an existing-product reader. Changing any draft value, image binding or linked dependency requires a new preparation read. A valid revision does not reserve backend state or exclude concurrent console changes.

A verified preparation points to the selected shop's products/create screen. It is not a save.

Inputs

Input example

Illustrative single-option draft. Replace image and shipping IDs with completed/observed same-context values. The earlier upload dry run does not create shop-image-001.

{
  "channelCode": "selected-channel",
  "pAppCode": "X00004",
  "draft": {
    "name": "Sample notebook",
    "slug": "sample-notebook",
    "price": "1000",
    "originalPrice": null,
    "imageTaskIds": ["shop-image-001"],
    "returnPolicyContent": "Use the existing store return policy.",
    "shippingPolicyId": "observed_shipping_policy",
    "saleStatus": "DISCONTINUED",
    "visibilityStatus": "DISABLED",
    "options": {"kind": "single", "sku": "NOTEBOOK-01", "quantity": 10}
  }
}

Optional creation SEO fields

None accepts null. The three plain string fields are not trimmed. Omitted keys remain absent from the draft and generated request; there are no new defaults or implicit name/summary copies. The source UI can prefill title/description on name/summary blur, but this adapter does not synthesize those values. Partial metadata leaves other SEO keys absent. Legacy X00002 and ticket-event drafts do not gain these fields.

Any metadata edit requires preparing the entire draft again and using the newly returned revision. In the owner workflow, requested metadata joins exact product/image/option/stock readback. Missing keys, changed keyword order/duplicates, or null in place of an explicit empty string remain pending. Creation receipts and sent-once recovery are unchanged. This does not implement a search-engine indexing result, visitor metadata rendering or exact deletion/restoration.

The following input-schema illustration demonstrates explicit blanks and retained duplicate keyword order. Real image/dependency identities and the existing prerequisites are still required.

{
  "channelCode": "selected-channel",
  "pAppCode": "X00004",
  "draft": {
    "name": "Sample notebook",
    "slug": "sample-notebook",
    "price": "1000",
    "originalPrice": null,
    "imageTaskIds": ["shop-image-001"],
    "returnPolicyContent": "Use the existing store return policy.",
    "shippingPolicyId": "observed_shipping_policy",
    "saleStatus": "DISCONTINUED",
    "visibilityStatus": "DISABLED",
    "options": {"kind": "single", "sku": "NOTEBOOK-01", "quantity": 10},
    "seoTitle": "Notebook",
    "seoDescription": "",
    "seoKeywords": ["notebook", "paper", "notebook"],
    "seoImgAltText": ""
  }
}

Initial buyer input and add-ons

These are initial child records within the existing CREATE; they do not add new tools or enable adding groups/items to an existing product. It reuses the owner field constraints, allows at most one input/group and validates ordered1–3-item arrays with isRequired:false.

Neither object accepts null, existing child IDs, caller-selected ranks, requiredness or arbitrary extra fields. Add-ons use one group with isRequired:false; child ordering is derived from the input. Prices use the verified currency and the existing add-on rule: zero through9,999,999,990, KRW integer strings in steps of100 and USD steps of0.01. KRW decimal notation is rejected even for an integral value. These bounds differ from the base product/variant price rules. USD prices are normalized to two decimals; no currency conversion or buyer charge occurs.

Omitted inputOption/addons introduce no parsed defaults and retain the older empty request arrays. They can compose with single/combined variants and explicit SEO in the owner workflow. Editing any option requires fresh preparation of the complete draft and a new revision. The existing image, linked-record, stock and sale/visibility checks remain required.

The durable returned product ID identifies the created aggregate. Two stable reads of that exact product validate child business/numeric IDs, parent/store/currency identity, uniqueness, order, requested title/placeholder/price/status and unchanged surrounding product state. Generated child identities and timestamps are excluded only from the requested-value projection; child IDs remain in the full stability comparison. Missing parent identity cannot be recovered by matching child text or IDs from a search.

Illustrative input-schema draft with initial options. Use real same-context image and shipping identities.

{
  "channelCode": "selected-channel",
  "pAppCode": "X00004",
  "draft": {
    "name": "Sample notebook",
    "slug": "sample-notebook",
    "price": "1000",
    "originalPrice": null,
    "imageTaskIds": ["shop-image-001"],
    "returnPolicyContent": "Use the existing store return policy.",
    "shippingPolicyId": "observed_shipping_policy",
    "saleStatus": "DISCONTINUED",
    "visibilityStatus": "DISABLED",
    "options": {"kind": "single", "sku": "NOTEBOOK-01", "quantity": 10},
    "inputOption": {"title": "Gift message", "placeholder": "Enter a short message"},
    "addons": {
      "title": "Gift wrapping",
      "items": [{"name": "Paper wrap", "additionalPrice": "100", "saleStatus": "ACTIVE"}]
    }
  }
}

Sent-once creation, historical status and observation-only recovery are unchanged. There is no automatic cleanup, rollback or identity-preserving removal.