​

Tango Vendor One-to-Many Inbound — File

Generated from Tango Vendor_OnetoMany Integration Design Specification V0.4.docx in SharePoint folder 01 Common Integrations. OAS spec: vendor-inbound-onetomany.yaml

​

Overview

SFTP file-based inbound for clients where a single supplier maintains many sites. Each pipe-delimited row carries BOTH supplier-level data (the same on every row for a given supplier) AND site-level data. Multiple rows with the same Supplier_number represent multiple sites under that supplier. Same SFTP path and naming as the standard vendor-inbound-file — Tango disambiguates by row shape (presence of supplier-level columns alongside site-level ones). Owner: Tango Analytics Spec version: 0.4 Status: Draft (auto-generated — needs review)

​

Transport

​

Differences from standard Vendor file

​

Out-of-scope

• Linking the vendor to a lease or project (UI only).
• Adding / updating contacts attached to the vendor (UI only).

​

Integration logic

• Supplier_number is the supplier upsert key; Supplier_Site_Number is the site upsert key (under that supplier).
• Tango never deletes vendors. Inactivate via Supplier_Status = I.
• Empty / header-only → no data sent in the file warning.

​

Data fields (required ✅)

​

Supplier-level (PascalCase)

​

Site-level (snake_case)

​

Open Questions / Assumptions

• Same SFTP path as standard Vendor file — both vendor-inbound-file and this variant land at /inbound/vendor. Tango distinguishes by file content shape. Confirm whether separate paths are expected in production.
• Mixed-case field names — supplier-level fields use PascalCase, site-level fields use snake_case. Confirm intentional (or a doc inconsistency).
• Supplier_Site_Number PascalCase with underscore is unusual for snake-case’d “site” fields.
• SFTP credentials are <TBD>.
• Timing/frequency is <TBD>.
• No Supplier_Address3 field in source (just Address1/Address2), but site has address_3. Confirm asymmetry.

​

Changelog