This is the tool's core workflow: turning a scheduled LightReach install into a purchase order that's created in NetSuite, filed to the project, and emailed to CED, without hand-building anything.

The region view

Open PO GENERATION, then RESIDENTIAL. A row of region tabs (Austin, Dallas, Houston, San Antonio, Orlando, Tampa) sits under it. Pick a region to see its scheduled installs.

The Austin list: installs grouped by week, a status tag on every row, and the actions that status allows.

The Austin list: installs grouped by week, a status tag on every row, and the actions that status allows.

The header gives the region and a one-line summary, for example "9 installs scheduled through Wed 10/21 · 6 need action". On the right are MANUAL PO (see 3a) and the batch button GENERATE N DIRECT PAY POS.

Which installs are listed. The list runs from today through the end of next week, on Central time. On Thursday and Friday it reaches further, through Wednesday of the week after, so Monday to Wednesday installs show up while there is still time to order for them. Rows are grouped under week headings: This week, Next week, then Week of 10/19 and so on.

What stands out. Only the status tag is colored. A row that needs action has an orange bar on its left edge, and its install date turns orange when it is 5 days away or less.

Each project row shows:

Column Meaning
PROJECT The Sunrise project ID
CUSTOMER The customer name, plus a warning such as No Lightreach account ID when something blocks the PO
PROGRAM Direct Pay or Kitted; this decides how the PO is made
INSTALL The install date and how far away it is, for example Tue 10/13, in 4 days
KW System size in kW
STATUS Needs PO, Needs reconcile, PO sent or No PO needed (see the table below)
ACTIONS The buttons that status allows, plus the ⋮ menu

Program types & filters

The toggle above the table filters by program: All, Direct Pay and Kitted, each with a live count. The program shows on each row as a small outlined tag, Direct Pay or Kitted.

Austin filtered to Kitted (3): every row is a CED Kitted job, with RECONCILE or REOPEN as its action.

Austin filtered to Kitted (3): every row is a CED Kitted job, with RECONCILE or REOPEN as its action.

Status tag Means Row actions
Needs PO (amber) A Direct Pay install with no PO yet GENERATE PO; the ⋮ menu adds Generate PO without emailing CED
Needs reconcile (amber) A Kitted install with no PO yet RECONCILE, which checks the kit against warehouse stock first
PO sent (green) The project has a PO; click the tag to open it in NetSuite SEND TO CED (email it again), UPDATE PO (re-sync with the Sales Order and send the update), RETURN (request a material return); the ⋮ menu adds Open PO in NetSuite
No PO needed (gray) A Kitted job marked complete without a PO REOPEN

When the project has a LightReach account ID, the ⋮ menu also has Open in Lightreach (<account id>). A Direct Pay project without one shows No Lightreach account ID in orange under the customer name.

Happy path A: generate a whole region (Direct Pay)

  1. Select the region tab. Every Direct Pay project that still needs a PO starts checked; nothing else can be checked.
  2. Uncheck any you want to skip.
  3. Click GENERATE N DIRECT PAY POS in the header (N is the number checked).