Skip to content

URS-062 · Order Type Options (Dropship, Consignment, Direct Sales)

Title: Order Type Options (Dropship, Consignment, Direct Sales) Date: 2026-04-23T03:44:42.590Z Duration: 161.2s Overall Status: ✅ PASS

The system shall allow a user to select multiple order types.

Source: User_Requirement_Specifications_ZuriMED_DeviceFlow.xlsx — the run below proves the system meets this requirement.

Status: ✅ PASS

Each step below corresponds to one Playwright test that ran sequentially. Screenshots and video recordings provide visual evidence of the UI behaviour.

1. Step 1: Login as sales rep — ✅ PASS

Section titled “1. Step 1: Login as sales rep — ✅ PASS”

What this step proves:

Proves that Bob Kauffman (StellarTech Sales Rep) can authenticate and reach the order creation form. Establishes the user context for all subsequent steps.

Screenshots:

step 01 logged in

step 01 order creation form

Video recording:


2. Step 2a: All order types visible — ✅ PASS

Section titled “2. Step 2a: All order types visible — ✅ PASS”

What this step proves:

After selecting an account delivery location, all three order types — Consignment, Direct Order, and Drop-ship — are simultaneously visible and Consignment is the default selection. This satisfies the URS-062 requirement that order type options are context-dependent on the chosen delivery location.

Screenshots:

step 02 all order types visible

Video recording:


3. Step 2b: Trunk hides order type selector — ✅ PASS

Section titled “3. Step 2b: Trunk hides order type selector — ✅ PASS”

What this step proves:

Negative case for the context-dependent UI rule. Selecting the trunk delivery radio hides the order-type selector entirely — there are zero input[name="orderType_display"] radios rendered. Trunk deliveries are implicitly typed as “trunk” and do not expose the Consignment / Direct / Drop-ship options available to account deliveries.

Screenshots:

step 02b trunk no order type selector

Video recording:


4. Step 3: Select order types — ✅ PASS

Section titled “4. Step 3: Select order types — ✅ PASS”

What this step proves:

Each order type can be selected independently. Selecting Drop-ship reveals the “Receiving Rep” selector; selecting Consignment or Direct Order hides it. Confirms context-dependent UI responds correctly to user input.

Screenshots:

step 03 direct order selected

step 03 dropship selected with rep

step 03 consignment selected

Video recording:


5. Step 4: Change delivery location — ✅ PASS

Section titled “5. Step 4: Change delivery location — ✅ PASS”

What this step proves:

Changing the delivery location from one account to another keeps all three order type options visible without a page reload, confirming the UI updates reactively and the order type selector is not cleared when the location changes.

Screenshots:

step 04 boss order types

step 04 copley order types

Video recording:


What this step proves:

A complete consignment order is created and submitted end-to-end. The success screen confirms the order request was accepted with order type “Consignment”, proving the consignment flow is fully operational.

Audit events generated by this step:

(Evidence scoped to step execution window: 2026-04-23T03:46:06.927Z → 2026-04-23T03:46:20.436Z)

TimeTypeActionUserOrgPerformed
2026-04-23 03:46:17Zdecisionorder_request_createdbob.kauffman@stellartech.comZuriMEDyes

Screenshots:

step 05 consignment step2

step 05 consignment products

step 05 consignment review

step 05 consignment submitted

Video recording:


What this step proves:

A complete direct sales order is created and submitted end-to-end. The success screen confirms the order request was accepted with order type “Direct”, proving the direct sales flow is fully operational.

Audit events generated by this step:

(Evidence scoped to step execution window: 2026-04-23T03:46:31.077Z → 2026-04-23T03:46:44.585Z)

TimeTypeActionUserOrgPerformed
2026-04-23 03:46:41Zdecisionorder_request_createdbob.kauffman@stellartech.comZuriMEDyes

Screenshots:

step 06 direct step2

step 06 direct products

step 06 direct review

step 06 direct submitted

Video recording:


What this step proves:

A complete dropship order is created and submitted end-to-end. The success screen confirms the order request was accepted with order type “Drop-ship”, proving the dropship flow — including the Receiving Rep selector — is fully operational.

Audit events generated by this step:

(Evidence scoped to step execution window: 2026-04-23T03:46:57.133Z → 2026-04-23T03:47:12.970Z)

TimeTypeActionUserOrgPerformed
2026-04-23 03:47:09Zdecisionorder_request_createdbob.kauffman@stellartech.comZuriMEDyes

Screenshots:

step 07 dropship step2

step 07 dropship products

step 07 dropship review

step 07 dropship submitted

Video recording:


What this step proves:

The orders list is inspected after all three submissions. The recently created consignment, direct, and dropship orders are all visible, confirming the system persisted each order type correctly and all three types appear in the same list view.

Screenshots:

step 08 orders list

Video recording:


The following SQL queries ran against the application database after the Playwright scenarios completed. Each query asserts a specific condition that proves the feature under test persisted its data correctly.

Recent orders created by test user — ✅ PASS

Section titled “Recent orders created by test user — ✅ PASS”

Assertion: At least one order should have been created during the test

SELECT id, request_number, order_type, status, location_id, sales_account_id, created_at
FROM order_requests
WHERE requested_by_user_id = $1
AND notes LIKE '%URS-062%'
ORDER BY created_at DESC
idrequest_numberorder_typestatuslocation_idsales_account_idcreated_at
019db872-e06d-792a-aba6-7ac02c05de49OR-3dropshipsubmitteda3e7f8a9-b0c1-2345-0123-4567890123452ac9d0e1-f2a3-4567-2345-6789012345672026-04-23T03:47:09.538Z
019db872-71a1-72ed-aaac-698d95ff17aeOR-2directsubmitted81c5d6e7-f8a9-0123-8901-2345678901231fb8c9d0-e1f2-3456-1234-5678901234562026-04-23T03:46:41.173Z
019db872-133e-7d5c-8615-932d8b7daa48OR-1consignmentsubmitted6ea3b4c5-d6e7-8901-6789-012345678901fea7b8c9-d0e1-2345-0123-4567890123452026-04-23T03:46:17.003Z

Assertion: A consignment order should exist from the test run

SELECT id, request_number, order_type, status, sales_account_id
FROM order_requests
WHERE requested_by_user_id = $1
AND order_type = 'consignment'
AND notes LIKE '%URS-062%'
ORDER BY created_at DESC
LIMIT 1
idrequest_numberorder_typestatussales_account_id
019db872-133e-7d5c-8615-932d8b7daa48OR-1consignmentsubmittedfea7b8c9-d0e1-2345-0123-456789012345

Assertion: A direct order should exist from the test run

SELECT id, request_number, order_type, status, sales_account_id
FROM order_requests
WHERE requested_by_user_id = $1
AND order_type = 'direct'
AND notes LIKE '%URS-062%'
ORDER BY created_at DESC
LIMIT 1
idrequest_numberorder_typestatussales_account_id
019db872-71a1-72ed-aaac-698d95ff17aeOR-2directsubmitted1fb8c9d0-e1f2-3456-1234-567890123456

Dropship order created with receiving rep — ✅ PASS

Section titled “Dropship order created with receiving rep — ✅ PASS”

Assertion: A dropship order should exist from the test run and have receiving_rep_user_id populated

SELECT id, request_number, order_type, status, sales_account_id, receiving_rep_user_id
FROM order_requests
WHERE requested_by_user_id = $1
AND order_type = 'dropship'
AND notes LIKE '%URS-062%'
ORDER BY created_at DESC
LIMIT 1
idrequest_numberorder_typestatussales_account_idreceiving_rep_user_id
019db872-e06d-792a-aba6-7ac02c05de49OR-3dropshipsubmitted2ac9d0e1-f2a3-4567-2345-67890123456717b8c9d0-e1f2-3456-1234-567890123456

All three order types present — ✅ PASS

Section titled “All three order types present — ✅ PASS”

Assertion: Orders of all three types (consignment, direct, dropship) should exist

SELECT order_type, COUNT(*) as order_count
FROM order_requests
WHERE requested_by_user_id = $1
AND notes LIKE '%URS-062%'
GROUP BY order_type
ORDER BY order_type
order_typeorder_count
consignment1
direct1
dropship1

All orders have delivery locations — ✅ PASS

Section titled “All orders have delivery locations — ✅ PASS”

Assertion: Every order should have a delivery location assigned

SELECT orq.id, orq.order_type, orq.location_id, orq.sales_account_id,
rwl.name as location_name, rwl.type as location_type
FROM order_requests orq
LEFT JOIN real_world_locations rwl ON rwl.id = orq.location_id
WHERE orq.requested_by_user_id = $1
AND orq.created_at > NOW() - INTERVAL '30 minutes'
ORDER BY orq.created_at DESC
idorder_typelocation_idsales_account_idlocation_namelocation_type
019db872-e06d-792a-aba6-7ac02c05de49dropshipa3e7f8a9-b0c1-2345-0123-4567890123452ac9d0e1-f2a3-4567-2345-678901234567Connecticut Ortho - Shippingasc
019db872-71a1-72ed-aaac-698d95ff17aedirect81c5d6e7-f8a9-0123-8901-2345678901231fb8c9d0-e1f2-3456-1234-567890123456Copley Hospital - Shippinghospital
019db872-133e-7d5c-8615-932d8b7daa48consignment6ea3b4c5-d6e7-8901-6789-012345678901fea7b8c9-d0e1-2345-0123-456789012345BOSS - Shippinghospital

Every row written to audit_events while this test was running (scoped to the demo organizations). Provides compliance evidence that user actions are traced end-to-end (URS-003).

Capture window start: 2026-04-23T03:44:40.666Z

SELECT
ae.created_at,
ae.event_type,
ae.action,
ae.user_id,
u.email AS user_email,
ae.organization_id,
o.name AS organization_name,
ae.object_id,
ae.secondary_object_id,
ae.payload,
ae.route,
ae.trace_id
FROM audit_events ae
LEFT JOIN users u ON u.id = ae.user_id
LEFT JOIN organizations o ON o.id = ae.organization_id
WHERE ae.created_at >= $1
AND ae.organization_id = ANY($2::uuid[])
ORDER BY ae.created_at ASC

12 event(s) captured:

TimeTypeActionUserOrgObject IDPerformedReason
2026-04-23 03:44:45Zuser_loguser:loginbob.kauffman@stellartech.comStellarTech Medical Solutions
2026-04-23 03:44:53Zuser_loguser:loginbob.kauffman@stellartech.comStellarTech Medical Solutions
2026-04-23 03:45:08Zuser_loguser:loginbob.kauffman@stellartech.comStellarTech Medical Solutions
2026-04-23 03:45:18Zuser_loguser:loginbob.kauffman@stellartech.comStellarTech Medical Solutions
2026-04-23 03:45:38Zuser_loguser:loginbob.kauffman@stellartech.comStellarTech Medical Solutions
2026-04-23 03:45:58Zuser_loguser:loginbob.kauffman@stellartech.comStellarTech Medical Solutions
2026-04-23 03:46:17Zdecisionorder_request_createdbob.kauffman@stellartech.comZuriMED019db872-133e-7d5c-8615-932d8b7daa48yesOrder request OR-1 created (importSource=manual)
2026-04-23 03:46:21Zuser_loguser:loginbob.kauffman@stellartech.comStellarTech Medical Solutions
2026-04-23 03:46:41Zdecisionorder_request_createdbob.kauffman@stellartech.comZuriMED019db872-71a1-72ed-aaac-698d95ff17aeyesOrder request OR-2 created (importSource=manual)
2026-04-23 03:46:45Zuser_loguser:loginbob.kauffman@stellartech.comStellarTech Medical Solutions
2026-04-23 03:47:09Zdecisionorder_request_createdbob.kauffman@stellartech.comZuriMED019db872-e06d-792a-aba6-7ac02c05de49yesOrder request OR-3 created (importSource=manual)
2026-04-23 03:47:14Zuser_loguser:loginbob.kauffman@stellartech.comStellarTech Medical Solutions