DJUST is not just a transactional engine — it offers a modular, collaborative solution, purpose-built for the expectations of B2B buyers.

The purchasing flow has been reimagined around three key pillars:

1️⃣ Flexibility - Adapt cart usage to diverse business workflows

2️⃣ Performance - Handle thousands of product lines with ease

3️⃣ Collaboration - Move from a solo tool to a shared, multi-account experience

---

General Definition

Carts and orders are two essential components of the B2B purchasing process. They allow users to select products, prepare purchases, and finalize transactions on the platform.

• The cart is a temporary space where users gather items before confirming a purchase. It allows for quantity changes, offer comparisons, and order preparation.
• The order represents a purchase. Once confirmed, it is routed to fulfillment and billing processes.

Though related, carts and orders serve different purposes in the buyer journey:

---

Detailed Definitions

Cart

A cart in DJUST is a temporary container used to group products before placing an order.

Key Characteristics

• Can contain multiple product lines with adjustable quantities
• Can contain products from multiple suppliers
• Linked to a specific Customer User and account
• Can be updated anytime (add/remove lines, update quantities)
• Can be saved as a buying list for future purchases
• Complies with account-specific pricing and purchasing rules
• Users can manage multiple carts in parallel (e.g., per supplier or use case)

---

Order

An order in DJUST is the final expression of a purchase, created from a validated cart.

Key Characteristics

• Created upon validation of a cart
• Follows a defined workflow with statuses such as Draft, Created, Waiting Approval, Shipped, etc.
• Has two status types:
  • Payment status - (if payment is activated in your environment)
  • Logistic status
• Can be modified depending on its current status, either by the user or the operator
• Includes detailed information (products, prices, billing/shipping addresses, payment methods, etc.)
• Can be exported to external systems (ERP, WMS, etc.)
• Can be split into multiple sub-orders based on logistics (e.g., different suppliers or warehouses)

---

Checkout Implementations

DJUST currently supports three versions of checkout, each adapted to a different stage of the platform’s evolution and use cases.

👍

Note

Checkout v3 brings the logic even closer to real B2B practices, such as purchase order modeling and minimal friction in validation workflows.