Jolt Arc Lighters / Project case study
2018Recorded work
Founder
From a wholesale request
to a checked,
usable order.
Jolt Arc Lighters needed wholesale requests entered as checked, usable orders. Noah documented and taught the process from incoming request to order entry, including historical backfill, checking and confirmation that order details were sent.
- Project type
- Historical operations
- Contribution
- Process documentation, hands-on training and exception handling
- Project status
- Manual operating procedure with saved-order and send confirmation
Tools & working context
Project scope and implementation.
- Trello
- WooCommerce / WordPress
- Google Docs SOP
- Product variants
- Order and tax review
01 / Business context
The problem
to solve.
Wholesale requests arrived through several channels. An administrator needed enough structured information to select the right customer, currency, product variants, quantities and pricing without depending on an informal handoff.
A written operating procedure and Trello queue organized the work. Noah demonstrated store entry and explained the checks and exceptions an administrator needed to handle.
Inside the workflow
A closer look
at the handoffs.
Start with the main path and its branches. Select a step for context, or switch to the technical map for implementation detail.
- Email order request
An incoming email supplies the source order information. - Phone order request
A telephone request is captured for administrative entry. - Message order request
SMS or message requests enter the same operating procedure. - Structured Trello order queue
Normalize the request into work with its original information available. - Check currency and customer
The operator selects currency, finds the customer and checks saved address details. - Enter products and pricing
Check variants, quantities and wholesale prices against the request. - First-order display rule
A first-order display is conditional; the repeat-customer example does not receive it. - Review and correct tax
The fuller walkthrough detects omitted tax and recalculates the order. - Handle already-paid backfill
Set the appropriate historical paid/completed state for the demonstrated order. - Save and send order details
The application confirms the updated order and send action. - Include first-order display
Apply the extra display rule when the source order is the customer’s first order. - Repeat customer: skip display
The demonstrated repeat order continues without the extra first-order display.
Read the workflow notes
- 01 / Structure
Normalize the incoming request
Requests from email, phone or messages became Trello work for administrative entry. The procedure made the source request available while the operator created the store record.
- 02 / Enter
Check the customer and order context
The demonstration selected the currency and existing customer, populated saved billing and shipping details, and added product variants, requested quantities and wholesale pricing.
- 03 / Review
Resolve the already-paid exception
The example customer had already paid, according to the narration. The operator reviewed the record, corrected omitted tax, updated its historical paid/completed state and triggered the order-details send action.
This is an operations and training example. The fuller demonstration backfills an already-paid order; setting a paid status is not evidence of a new payment transaction.
03 / Implementation detail
The checking step
is part of
the procedure.
The source order guided currency and customer selection. Saved customer information reduced re-entry, while the operator still checked whether the resulting address and contact fields were complete.
Product variants, quantities and wholesale prices needed to agree with the request. A first-order display rule was conditional; the repeat-customer example did not receive the extra display.
The demonstration caught a missing-tax issue and recalculated the order. It also corrected an initially unsuccessful status update, making the training useful as an example of real checking rather than an idealized click sequence.
The application confirmed “Order updated and sent,” and later screens retained the paid/completed state. That confirmed the saved action, but did not show the email arriving or the warehouse shipping the order.
An earlier, shorter recording stopped during an unresolved customer lookup. The fuller walkthrough supplies the completed record shown here; the two recordings are not presented as one uninterrupted successful run.
04 / Outcome & scope
Result
and scope.
The fuller walkthrough entered and reviewed a WooCommerce order, handled its already-paid history and received a send confirmation. The written procedure and training explained how another administrator could follow the process.
The demonstration did not collect a new payment, confirm email receipt or show shipment. No time-saving or error-reduction measure was recorded. Noah’s contribution was process maintenance, training and hands-on execution within a team.