In X-1, certain products are structured using a parent-child relationship, where one “parent” product is linked to multiple “child” products. This structure helps organize related items efficiently and allows certain settings and behaviors to cascade from parent to child.
📦 Example: Fuel as a Parent Product
Consider Fuel as the parent product. Its child products might include:
Jet-A
Avgas
Diesel
Gasoline
While each child product functions independently, the parent product’s configuration can directly influence how the child products behave within the system.
⚙️ How This Impacts Settings
Each product has specific settings that determine how it should appear on an invoice generated from a request. One critical setting is whether a product appears “As Item” or “As Service.”
When a child product (e.g., Jet-A) is set to display “As Item” (pulling gallon qty from a fuel ticket),
✅ it will only work correctly if the parent product (Fuel) is also set to “As Item.”If there’s a mismatch—e.g., Fuel is set to “As Service” and Jet-A is set to “As Item”—the system will not behave as expected.
❌ This may result in Jet-A not appearing on the invoice, or the fuel quantity not showing at all.
💲 How This Impacts Price Rules
Parent-child logic also affects how price rules are applied:
If a price rule is assigned to the parent product (Fuel), it will automatically apply to all child products (Jet-A, Avgas, Diesel, etc.).
However, if a price rule is assigned to a specific child product (e.g., Jet-A),
➡️ it will only apply to that child and not to its siblings (like Avgas or Diesel).
🧠 Key Takeaway
If you notice unexpected behavior with a child product (e.g., incorrect pricing, missing quantities on invoices, etc.), always review the parent product’s configuration first. Settings at the parent level could be silently overriding or conflicting with the child’s setup.
Need Help?
Still have questions? Contact the X-1 Support Team anytime — we’re happy to assist you.