Lifetime Replacement Parts

Concepts

Understand the core building blocks of the Lifetime Replacement Parts system.

last updated · apr 22, 2026 · 4 min read · edit this page →

1. Orders

An order represents a single purchase from a vendor. It has a unique order number, a date, a total cost, and a list of parts. The order is the parent container that gives all your individual parts their context.

2. Parts

A part is a specific item you purchased, such as an oil filter or a control arm. Each part belongs to an order and has a part number, a name, a quantity, and a unit price. When you search your ledger, you are usually searching for parts.

3. Vendors

Vendors are the stores where you buy your parts (for example FCP Euro, Pelican Parts, and ECS Tuning). They each have their own receipt format, email structure, and warranty workflow. Lifetime Replacement Parts supports a specific list of vendors to keep parsing and order links accurate.

4. Warranty Policies

Different vendors have different warranty policies and claim steps. For instance, one vendor may ask for a PDF form while another may use account history or email. Lifetime Replacement Parts helps you track which parts from which orders may be eligible under those policies.

// note
Eligibility flags are tracking aids, not claim submissions. Always follow the vendor's current claim instructions before shipping parts back or requesting credit.

5. Ingestion Rules

Ingestion rules are small, declarative if/then statements evaluated against every order that hits your account. They allow you to automate actions like tagging parts, advancing status, or linking to projects based on the vendor, amount, or part numbers.

6. Projects

Projects are logical groupings of parts across different orders. If you're rebuilding an engine, you might buy parts from three different vendors over two months. You can link all those parts to an "Engine Rebuild" project to track total spend and progress.

// docs maintenance
Keep docs updated with product, API, UI, and workflow changes. If behavior changes, the matching docs page should change in the same work.