Credit pricing15-360 day ladderAdmin controls module enablement; seller values are saved with listing readback.
Seller fill controlidentity / technical / traceability / stock / pricing / deliveryModule section map is explicit so required, optional, buyer-visible, and admin-reviewed areas stay separated.
Variant / design buyingSKU / Size / Color / Design number / SKU/lot / Photo/video setDesign, style, lot, batch, size, color, model, or service-report keys remain module-specific.
Traceability carry-forwardSource lot / Supplier/origin / Certificate / Buyer order carry forward / B2 C mode controls tax inclusive display and return policy / Retail productBuyer-side reuse is tied to source listing, lot, report, process, and order context instead of retyping.
Source traceability prefillPull previous buy, lot, report, or listing proofUse this when a seller bought or processed an earlier product and needs known design, lot, material, lab, machine, and document proof carried into the next listing.Seller still confirms new processing, machine used for this stage, new quantity/waste, price, tax, packing, delivery, and commercial terms.
Automation matrixModule-specific linked-field model: Family / Material / Specification / Process / Machine / Commercial Basis / Sku / Size Color / Consumer Price / Tax Display / Return Policy / StockFamily -> Material required / Material -> Specification required / Specification -> Process required / Process -> Machine / Machine -> Commercial Basis / Sku -> Size Color required / Consumer Price -> Tax Display required / Return Policy -> Delivery
Live linked-field selectorSelections alignedChoose an upstream value and the next module-specific field becomes available. Downstream choices are retained with warning instead of silently deleted.
Dependency contract is aligned for current values.
AttachmentsProduct images / Invoice/reference document / Photos / Videos / DocumentsPhotos, videos, reports, drawings, samples, and certificates follow the same seller listing payload.
Buyer selection matrixSKU / Size/color / Consumer price / Tax display / Return policy / Stock / Delivery / SizeBuyer can choose design, style, SKU, lot, model, report, size, color, stock, MOQ, or service slot according to module behavior.
Matrix completeness contractSKU / Size/color / Consumer price / Tax display / Return policy / Stock / Delivery / Size / SKU / Customer order / Invoice id / Return/warranty record / Size / Color / Design number / SKU/lotDesign/style/article/SKU, photo/video, quantity slab, stock by variant, safety proof, sample approval, and carry-forward references are visible through this existing shared seller engine.
Carry-forward payloadSKU / Customer order / Invoice id / Return/warranty record / Size / Color / Design number / SKU/lotNext buyer or next process can reuse source listing, lot, design, report, process, order, invoice, and dispatch references.
Dependency contractFamily -> Material required / Material -> Specification required / Specification -> Process required / Process -> Machine / Machine -> Commercial Basis / Sku -> Size Color required / Consumer Price -> Tax Display required / Return Policy -> DeliveryShared / Textile / Dependency chain / Admin configurable / Module specific / Retail / Sku consumer tax
Module business behaviorretail New Arrival can trend when eligibleModule logic stays inside this schema instead of a duplicate route or generic copy.
Seller listing workflow
Textile Retailers
Complete the listing from product details through RFQ, order, dispatch, and payment setup.
1. Trade and account context
Selected seller business - ACTIVE
Confirm seller business
Check personal or business account
Confirm buyer-visible role context
2. Module and product master
Confirm the textile module, product master, seller SKU, and listing title before adding commercial details.
3. Listing type and New Arrival
Select Fresh, FreshMix, Lot, JobLot, Seconds, or Claimless independently from New Arrival eligibility.
Complete module-specific construction, process, job-work, machinery, service, Dobby, or Jacquard fields where applicable.
6. Quantity, MOQ and stock
2400 unit / storefront channel pending / pickup to confirm
7. Pricing and slabs
INR 620 per unit with MOQ pending
8. Payment, advance and credit
Set payment terms, advance, credit or PDC slabs, and release windows supported by this module.
9. Domestic/export and tax
Set domestic or export mode, country, origin, currency, tax label, incoterm, port, and delivery scope.
10. Packaging and CBM
Add packaging, dimensions, gross/net weight, CBM, and shipment handling details.
11. Images and documents
Add the documents buyers need for review. Each bucket shows whether a document has been added for this listing.
Product Photos: Not added
Catalog / Gallery Media: Not added
Store / Lot Photos: Not added
QC / Test Reports: Not added
Certificates: Not added
Export Docs: Not added
Invoice Docs: Not added
LC/PDC Docs: Not added
12. Policy visibility
Review return, refund, warranty, inspection, sample, and buyer-visible policy notes.
13. Preview
Review the buyer-facing product card, comparison details, RFQ details, and order handoff fields.
14. Save draft
Save the listing as a draft or update the existing seller-owned listing without changing module-specific fields.
15. Publish
Buyers can request SKU assortment, store channel, stock, invoice, return terms, and quote details. Accepted RFQs or direct orders move into SKU allocation, invoice, return policy, and buyer order tracking.
16. Edit and archive
Fulfillment uses seller-arranged dispatch with store pickup or shipment checks. Payment terms: Online; payout, invoice, credit, or return documents should be confirmed before publish.
Edit seller-owned listing
Archive when not available
Unarchive when available again
Loading seller business...
Active user: Canonical seller masterRole: sellerCompany: Company master
One-user mode map: one local user context can switch across buyer, seller, business, and personal surfaces. Guard evidence: SaaS status | workflow/RBAC status | identity gate=true | auth connector off=true | no SSO/MFA activation claimed
Create a textile retailers listing.
Seller master completionREADY: 24/24 seller-master page fields available
Module groupMarket / retail / trade modules
Save payload pathPOST /api/trade-core/listings/:moduleKey body.fields.sellerMasterPageCompletionPayload
Lifecycle state proofAPPROVED: lifecycle ACTIVE; approval PENDING_REVIEW; publication HIDDEN; publish request PENDING; archived NO
Lifecycle meaningApproved means admin review has passed, but buyer visibility still needs publication and buyerVisible proof.
Seller next actionClear readiness watch items before asking admin to publish so comparison, order, logistics, wallet, payout, and audit handoff stay clean.
Attachment Metadata (Prepare-Only)0 selected filenames captured into uploadMetadata and attachmentMetadataSnapshot.
PREPARE-ONLY / NO LIVE STORAGE PROVIDER. Metadata lifecycle only; no live storage provider, no file serving, and no backend route changes are enabled by this page.
schema trade-core-document-infrastructure-v1source route /api/trade-core/documents/foundationtable trade_documentslifecycle PREPARED metadata only
Product Photos
No files selected
Catalog / Gallery Media
No files selected
Store / Lot Photos
No files selected
QC / Test Reports
No files selected
Certificates
No files selected
Export Docs
No files selected
Invoice Docs
No files selected
LC/PDC Docs
No files selected
Buyer Requirement Docs
No files selected
Other Docs
No files selected
Dependency Contract Hints
Review mismatch warnings: downstream values are retained with warning.