YR Equipment Serial Number Dependency Map

The serial number is the physical ramp identity. Once the Genius equipment serials are clean, API calls can pull equipment records into Zoho as YR_Equipment records while availability remains workflow-owned inside Zoho.

YR equipment serial number dependency flow Genius serial number flows through sync validation into Zoho YR Equipment, then fans out to Sales Orders, automation, reports, and BOL tracking. Dirty serials are quarantined. SOURCE FIELD Genius equipment API: EquipmentSerialNumber Export/view: SerialNumber Example: ITZ20-22111476 Also carries Id, CustomerName, IsActive Used only as source identity data CLEANUP GATE Genius API sync GET EquipmentEntity Clean serials first Create/update Zoho fields Never overwrite status ZOHO IDENTITY RECORD YR_Equipment Name = serial Genius_ID Current_Customer Rental_Status One ramp DEPENDENCIES Sales Orders YR_Equipment slots 1-4 Workflow functions YR1, YR2, YR2b, YR3 Fleet reports Checked-out dashboard BOL tracking Future movement history DATA QUALITY RISKS Dirty serial values "Sold to..." prefixes Typos and missing zeros Width notes and suffixes Placeholders and inactive rows Quarantine Do not import Failure radius Duplicates, wrong ramp, false inventory
Source identity Automation or sync logic Zoho stored record Dependent Zoho process Risk or quarantine path

Dependent Processes

Equipment assignment

Initial Sales Orders use YR_Equipment through YR_Equipment_4. The lookup label is the serial, so a dirty label can assign the wrong physical ramp.

Availability automation

YR1 marks assigned ramps Checked Out. YR2 marks linked ramps Available. YR2b reverses back to Checked Out.

Monthly billing continuity

YR3 copies all equipment lookups from the initial SO to monthly charge SOs. A bad lookup propagates across follow-up orders.

Checked-out dashboard

The fleet report starts from YR_Equipment records where Rental_Status = Checked Out and displays serial from Name.

Genius API sync

After serial cleanup, an API job can pull EquipmentEntity records from Genius and create or update Zoho YR_Equipment identity fields.

Future BOL tracking

Movement history will attach to YR_Equipment. That only works if one clean equipment record represents one physical ramp.

Field Contract

System Field Role Cleanliness Requirement
Genius API EquipmentEntity.EquipmentSerialNumber Canonical live API serial. Physical identity only. Do not mix lifecycle notes into it.
Genius export/view SerialNumber Column B in equipment export used for Zoho sync. Rows starting with Sold to, inactive rows, placeholders, SUNBELT, and non-YR rows are excluded.
Planned sync job GET /api/data/fetch/EquipmentEntity Future automated pull from Genius into Zoho equipment records. Run only after serial cleanup rules are stable; update identity/reference fields, not Zoho availability.
Zoho CRM YR_Equipment.Name Visible serial and lookup label. Keep stable after SOs link to it. This is the user-facing ramp identity.
Zoho CRM YR_Equipment.Genius_ID ERP tie-back when serial text differs. Use it to avoid duplicates from typo or suffix mismatches.
Zoho CRM YR_Equipment.Rental_Status Availability state. Zoho workflows own this. Genius sync must not overwrite it.
The serial field should answer only one question: which physical ramp is this? Availability belongs in explicit status fields like Rental_Status and IsActive, not inside the serial string.

What Breaks When It Is Dirty

Issue Immediate Effect Downstream Damage
Sold to... prefix treated as active inventory Sold equipment appears as a selectable ramp. False availability, bad fleet counts, confusing SO lookup choices.
Typo, missing zero, or renamed serial Genius and Zoho do not match exactly. Duplicate equipment records or broken report joins.
Width notes, rental suffixes, or "also #..." One physical ramp gets multiple labels. Status can update the wrong record; BOL history splits later.
Placeholder serials No real ramp identity exists. Should not become a usable Zoho rental asset.
Manual deletion or rename after linking Existing SO lookups lose reliable meaning. Follow-up orders, reports, and future BOL history become suspect.