Skip to content

DSSL · B2B procurement

Partner Portal

A working specification, from intake to checkout.

38

“4 MP outdoor camera”, 8 units

Row 38: the source text beside three matches

Work
Commercial redesign shipped in full
Role
Sole designer; frontend, backend, PM, QA and team lead
Period
2024–winter 2026

Make space for the buyer

The archived dashboard foregrounded promotions and left destinations behind icons. I made the specification the working object, with named navigation and separate responsibilities for matching and commercial terms.

  1. Procurement tasks first
  2. Named destinations
The archived dashboard, with audit notes

A shared list

XLS import and Quick order feed the same resolution workspace. Cart, supply planning and checkout have distinct jobs. The map shows eight key screens.

Screen map Procurement workspace

Dashboard opens file import, Quick order, Cart and Order details. Both intakes share Resolution Center. Cart contains supply planning and checkout. Eight selected screens, not the entire product.

  • Dashboard leads to XLS import
  • Dashboard leads to Quick order
  • Dashboard leads to Cart
  • Dashboard leads to Order details
  • XLS import leads to Resolution
  • Quick order leads to Resolution
  • Cart leads to Supply plan
  • Cart leads to Checkout
Screen map Procurement workspace

Dashboard opens file import, Quick order, Cart and Order details. Both intakes share Resolution Center. Cart contains supply planning and checkout. Eight selected screens, not the entire product.

  • Dashboard leads to XLS import
  • Dashboard leads to Quick order
  • Dashboard leads to Cart
  • Dashboard leads to Order details
  • XLS import leads to Resolution
  • Quick order leads to Resolution
  • Cart leads to Supply plan
  • Cart leads to Checkout
Eight key screens of the procurement workspace

Choose a product, then check terms

Matching does not promise compatibility. Buyers choose or correct the item; Cart separately reviews commercial changes. Each decision has a visible return path before order creation.

User flow From XLS to order

Read imported lines. Unresolved identity requires buyer selection or correction and recheck. Cart separately reviews commercial change. Choose a supply plan, confirm terms, create an order. Source text after creation is not yet stored.

  • Upload XLS leads to Read lines
  • Read lines leads to Unresolved lines?
  • Unresolved lines? leads to Choose / correct (yes)
  • Choose / correct leads to Unresolved lines?
  • Unresolved lines? leads to Cart (no)
  • Cart leads to Commercial change?
  • Commercial change? leads to Accept / resolve (yes)
  • Accept / resolve leads to Cart
  • Commercial change? leads to Choose plan (no)
  • Choose plan leads to Confirm terms
  • Confirm terms leads to Order created
User flow From XLS to order

Read imported lines. Unresolved identity requires buyer selection or correction and recheck. Cart separately reviews commercial change. Choose a supply plan, confirm terms, create an order. Source text after creation is not yet stored.

  • Upload XLS leads to Read lines
  • Read lines leads to Unresolved lines?
  • Unresolved lines? leads to Choose / correct (yes)
  • Choose / correct leads to Unresolved lines?
  • Unresolved lines? leads to Cart (no)
  • Cart leads to Commercial change?
  • Commercial change? leads to Accept / resolve (yes)
  • Accept / resolve leads to Cart
  • Commercial change? leads to Choose plan (no)
  • Choose plan leads to Confirm terms
  • Confirm terms leads to Order created
From the right product to commercial terms to an order
  1. Keep the request beside the candidates

    Row 38 of office_north_v8.xlsx asks for “камера 4мп уличная”, eight units. The buyer compares three matches and chooses the second.

  2. Confirm the choice, retain the source

    The source text and quantity remain. Confirmed records the buyer’s decision; “was Ambiguous” retains the original matching category. Undo keeps the choice reversible.

  3. Carry the row into commercial review

    Cart identifies the chosen SKU as source row 38 and keeps quantity eight. Price and availability stay separate from product identity.

States make the next action explicit

Resolution rows retain the source request after a product is chosen. Availability records the warehouse response; shipment plans show whether supply is possible. A missing warehouse response reads “not confirmed”, never zero.

Product states

DSSL procurement system

Product choice

ResolutionRow
  1. Ambiguous · choose a match

  2. Confirmed · original category retained

Availability and supply

Availability
  1. Verified stock

  2. Not confirmed · no WMS response

FulfillmentPlan
  1. Selected · choice remains visible

  2. Unavailable · reason stated

Product choice, stock confirmation and shipment availability
Components in context · the same row after buyer confirmation

The commercial redesign shipped

The DSSL redesign shipped in full. I rebuilt the procurement scenario shown here with synthetic data.

Trade-off
Ambiguity still requires a buyer’s manual choice. Matching data cannot guarantee compatibility.
Evidence
Row 38 runs from product choice to Cart with its source text and quantity intact.
Next case: TRASSIR Learn

Let's talk

If the case above answered your question — or raised one.

Enlarged screenshot