Build on the supported package contract
Use @absolutejs/commerce-dubow through its supported public entry points.
@absolutejs/commerce-dubow
@absolutejs/commerce-dubowv0.2.0-beta.1betaCommerce & GrowthDubow design, catalog, pricing, and fulfillment integration for AbsoluteJS commerce
#Installation
BASH
bun add @absolutejs/commerce-dubow#Capabilities
Overview
Dubow catalog lookup, artwork, pricing and validated fulfillment serialization for AbsoluteJS commerce. Wire fields follow the official Dubow v2 documentation.
createDubowClient supports an injected fetch for isolated integration testing. createDubowCatalog preserves catalog identities but keeps variants unavailable until inventory, supplier SKU, price, imagery and decoration facts have been verified.
Fulfillment
validateDubowOrder(request, config) returns { valid, errors }. Call before collecting payment and again before release. serializeDubowOrder(request, config) validates and returns the single object accepted by client.submitOrders([order]). It performs no provider calls.
Config requires customerId, contactId, shipMethod and an explicit procurementType of Contract or Custom, unless each line supplies its trusted procurement override. Contract means customer-supplied garments; Custom means the agreed vendor sourcing arrangement. No procurement default is invented. Optional methodNames contains account-approved mappings for methods outside the supported defaults.
Each line retains supplier SKU in Name, style/mill and exact garment color in IntegrationProduct, and exact size/quantity in LineItemSizes. Its trusted metadata must include brand, styleCode, title, color, size, methods[] and artworkMappings[], with one method and mapping per artwork placement. A mapping requires status: ready, the matching placement, and providerLocation from the approved provider setup. Existing designs require numeric providerDesignId and providerColorwayCode; URL designs require the approved customerDesignCode, customer providerColorwayCode, and an HTTPS artwork URL. Never build this metadata directly from untrusted shopper fields.
Show 1 more
Mappings preserve embroidery, DTF, digital print, screen print and sublimation. Unknown methods, missing identities, and mismatched placements fail validation. Screen print requires 24 garments per approved design/colorway, counting combined sizes once per line. Account enablement, exact location values, source-art accessibility, and actual provider acceptance remain deployment checks.
Validation
bun run check:package runs type checking, mocked outbound-request tests and build/declaration output. Tests send no real orders.
Outcomes
What you can build
Hardening checklist
Production guidance
Make every external boundary explicitPin the deployed @absolutejs/commerce-dubow version, replace example or memory-backed dependencies with durable implementations, bound external calls, protect credentials, and emit enough evidence to retry or recover safely.
Follow in order
Troubleshooting path
1
Trace from the first failed boundary
Reproduce the smallest canonical @absolutejs/commerce-dubow example, confirm the supported entry point and version in the API explorer, then inspect the first boundary that did not produce its documented result.
#Public entry points
Supported entry points declared by this package manifest.
@absolutejs/commerce-dubowPackage entry point declared in package.json.
#Package commands
Scripts declared by this package manifest.
bun run buildbun build src/index.ts --outdir dist --target bun --external @absolutejs/commerce && tsc --noEmit false --emitDeclarationOnly --declaration --outDir dist
bun run check:packagebun run typecheck && bun run test && bun run build
bun run testbun test
bun run typechecktsc --noEmit