HandiRamp Order Ontology A cleaned ontology diagram explaining what an ontology is, then showing the HandiRamp order lookup ontology with lookup clues, resolver, ERP identity spine, evidence sources including all active Production Schedule 3.0 tabs and Returns – Kenosha monthly return logs, and CRM/UI endpoints. HandiRamp Order Ontology An ontology is not a source map. It is the shared company model of things, names, identifiers, and relationships that lets the lookup tool reason across messy systems. 1. WHAT AN ONTOLOGY IS 2. ORDER CLUES 3. RESOLVE ORDER IDENTITY 4. ENRICH AFTER RESOLUTION 5. RELATIONSHIP + ACTION Business things Order, customer, contact, shipment production job, invoice, note Names people use Zoho SO, Genius SO, WEB order Amazon ref, BOL, tracking Identifiers and joins which numbers mean the same thing and which ones do not Allowed relationships what can start a lookup what only enriches a resolved order Commerce order refs Woo, Veeqo, Amazon, vendor PO Zoho Sales Order inside-sales order handle often the number sales uses Human lookup hints email, customer name, tracking BOL / PRO when available Important distinction These are lookup handles. Some are origins; some are clues. Genius Sales Order SalesOrderHeader.Code PoNumber / customer / amount ERP identity spine operational order record joins most downstream facts Reference normalizer WEB-, AO-, HR-, bare number splits combined pallet refs Not every business process obeys this. Shipping systems FreightPop, Veeqo, Genius pkgdata carrier, tracking, ship status LTL Dashboard warehouse-maintained sheet shipper, BOL #, PRO/tracking Production Schedule 3.0 one worksheet, not separate systems Active tabs/views: ATT/AST · CVR-AV · SDR MISC · Closed · YR Stock in-house products only In-House Production Tracking dates, job #, completion welder, rush flag, shop status Returns – Kenosha monthly Return Log evidence exact order refs · part · qty · disposition Zoho Contacts + Notes contact identity, correspondence tracking-email note writeback Customer-service UI resolved identifiers order evidence cards Ontology failure case YR rental SO reuse breaks the 1:1 SO-to-SO bridge. Ontology rule No order identity? Evidence, not a lookup root. HandiRamp company ontology: orders are the business object; Zoho SO and Genius SO are both real company order handles; Genius SO.Code / PoNumber is the ERP join spine. LTL Dashboard and Production Schedule 3.0 enrich a resolved order; Returns – Kenosha matches only exact recorded resolved-order handles; none independently defines order identity.