Last updated: May 2026

Invoices and Quotes: From Estimate to Payment Tied to the Work That Earned It

Invoices and Quotes is the FireFlight app for quote-to-cash workflow. Build a quote from real line items, convert it to an invoice on approval, plus tie every entry back to the work order, project, part, or hourly service it represents. The audit trail follows the money from estimate through receipt.

Can FireFlight handle quote-to-cash with line items linked to actual work orders plus parts? Yes. Invoices and Quotes builds quotes with customizable line items, converts approved quotes to invoices in one click, plus auto-calculates taxes, discounts, plus totals. Every line ties to a task, a part, an hourly service, or a project template. Payment history per client, full audit trail, plus credits or adjustments post-invoice. Deployment runs weeks, not months.

FireFlight Invoices and Quotes screen showing quote-to-invoice workflow with line items linked to work orders plus project templates

See how an approved quote becomes an invoice in one click, with every line item still pointing back to the parts pulled plus the hours logged on the underlying work order. Live demo or a direct call.

Request a Demo Contact Us

Why does the billing department always re-key what operations already entered?

In 2026, most service operations still run a two-system billing process. Operations tracks the job in one tool: work orders, parts pulled, hours logged. Accounting tracks the invoice in another tool: QuickBooks, an old desktop billing app, or a homemade Excel template that started as a stopgap in 2018. Every invoice is a re-entry exercise. Somebody reads off the work order plus types it into the invoice. Somebody else compares the two systems at month end plus tries to explain the variance.

The cost is double-handling plus disputes. A line gets mistyped. A part qty drops a digit. The customer disputes the invoice because it does not match what their PO said the work covered. Accounting sends a credit memo. Operations gets pulled into a call to defend the original work. By the time the invoice clears, three people spent four hours on a job that billed for two.

Invoices and Quotes ends the re-entry. A quote gets built from the same line items that already live in Work Orders, Project Templates, plus Inventory Control. When the quote is approved, the conversion to invoice happens in one click. The line items never leave the source data. The customer sees a bill that matches the work because the bill was generated from the work.

How does a quote connect to actual operational records instead of free-text descriptions?

Every line on a quote can be tied to one of four sources: a task on a work order, a part in inventory, an hourly service rate, or a fixed-bid project template. When operations adds a new task to the work order, the quote can pull the task by reference. When inventory issues five units of a part, the quote line picks up the quantity plus the unit rate without manual transcription. Hourly service work pulls from labor logs. Fixed-bid project work pulls from the template that was scoped at sale.

Auto-calculation handles the math. Taxes apply per line based on jurisdiction rules. Discounts apply at the line or the document level. Totals roll up live as line items change. The quote can be sent as a print-ready PDF with company-profile branding applied automatically. Status flows through Sent, Accepted, Rejected, plus Converted, with timestamps at every state change.

Once the quote is accepted, conversion to invoice is a single click. The invoice carries the same line linkage. If a credit or adjustment is needed post-invoice, the change is recorded in the audit trail without overwriting the original document. Payment history per client plus per invoice rolls up into Accounts and Transactions, so accounting sees the same ledger the customer-facing team sees.

QuickBooks CSV Export PDF Branding

Your billing data is your evidence in a dispute. We treat it that way.

Quote plus invoice records live in encrypted storage hosted by PCG. Permission-based access governs who builds quotes, who approves them, plus who issues invoices, with a manager sign-off required above a configured threshold.

Every state change is logged with user identity plus timestamp. Credits, adjustments, plus reissues never overwrite the original document. The audit trail shows exactly what was quoted, what was accepted, plus what was invoiced, ready for an auditor, a customer dispute, or an internal investigation.

Ikhana, the FireFlight on-screen tutor character
On-Screen Tutor

Ikhana shows your team how to build a quote, tie its lines to operations, plus convert it to an invoice.

Every field, every dropdown, every approval step is explained the moment somebody asks. New billers issue their first quote the same week they start. No training queue. No tickets to IT.

Learn more about Ikhana

What does Invoices and Quotes give your billing team?

  • Build quotes with customizable line items plus terms drawn from real operational records, not free-text descriptions.
  • Convert approved quotes to invoices in one click. The line linkage to work orders, parts, plus services is preserved end to end.
  • Auto-calculate taxes by jurisdiction, plus apply discounts at the line or document level. Totals update live.
  • Track quote status: Sent, Accepted, Rejected, plus Converted, with timestamps on every state change.
  • Apply credits or adjustments post-invoice without overwriting the original document. The audit trail keeps every version.
  • Link quotes to tasks, parts, or hourly service items pulled directly from operations. Invoices link to recurring services or fixed-bid project templates the same way.
  • View full payment history per client or per invoice. Receipts, approvals, plus supporting documents attach directly.
  • Generate print-friendly PDFs with branding pulled from the company profile. Logos, terms, plus footers stay consistent.
  • Assign each quote or invoice to a business category for segmented reporting. The system slices billing by service line, region, or team without any manual tagging from the billing clerk.
  • Direct integration with Accounts and Transactions for ledger plus payment tracking. Export to CSV or PDF for accounting handoff.
  • Configurable payment reminders plus custom due dates. Works with Custom Reporting plus Ad-Hoc Reporting for AR visibility.
"We used to manage billing through email plus spreadsheets. Now it is centralized, accurate, plus automated."
ControllerNational Services Group

31 years of operational software, with AI reporting built in for 2026.

Phoenix Consultants Group has built custom operational software since 1995. Invoices and Quotes is one app inside the FireFlight platform, the same platform running fleet fueling for municipal operators, physician credentialing for staffing firms, plus airport ground equipment management for aviation services.

The AI layer added in 2026 means a controller can query Invoices and Quotes in plain English. "Show me every invoice over 30 days past due, grouped by client, with the originating work order plus the assigned account manager." The system answers from live data. No report request to IT. No waiting.

What changes operationally after Invoices and Quotes goes live?

  • Billing stops re-keying what operations already entered. The quote pulls from work orders, parts, plus labor logs at the source.
  • Customer disputes resolve faster. The invoice shows the exact line items, parts, plus hours that produced the total being challenged.
  • Quote-to-invoice latency drops from days to minutes. One-click conversion replaces the re-entry workflow that used to bottleneck closing the sale.
  • Month-end reconciliation stops being a manhunt. Operations plus accounting read from the same line items, with no system-to-system variance to chase.
  • AR visibility becomes live. The controller sees every aging invoice plus its originating work order without waiting for a custom report.

Frequently Asked Questions

Does Invoices and Quotes replace QuickBooks or just feed it?
+
Either, depending on how the deployment is configured. Some clients run their full quote-to-cash workflow inside FireFlight plus export ledger entries to QuickBooks for accountant-facing reporting. Others keep QuickBooks as the system of record for tax filings plus use Invoices and Quotes for the operational billing process up to the point of invoice issue. PCG configures the integration during deployment based on what your accounting team needs.
Can we handle both fixed-bid project billing plus time-and-materials billing in the same system?
+
Yes. A quote can mix fixed-bid line items pulled from a project template with hourly service lines pulled from labor logs plus parts lines pulled from inventory. The invoice carries the same mix. Auto-calculation handles the totals across line types so the customer receives one document that reflects the actual structure of the work.
What happens when a customer disputes a line on an invoice?
+
A credit or adjustment can be issued without overwriting the original invoice. The audit trail preserves both the original document plus the adjustment. The disputed line points back to the underlying work order, part record, or labor entry that generated it, so the dispute can be resolved from the operational record rather than from a re-typed description.
Can we set up recurring invoices for service contracts?
+
Yes. Recurring service contracts can be configured with their own cycle (monthly, quarterly, annual) plus auto-generation rules. The system issues the invoice on schedule, pulls line items from the active contract template, plus posts the entry to Accounts and Transactions. Manual review can be required before issue or the cycle can run fully automated depending on client preference.
How do payment reminders plus custom due dates work?
+
Each invoice carries a due date plus an optional reminder schedule. Reminders can fire by email at configurable intervals before plus after the due date. Custom terms (Net 15, Net 30, Net 60, or client-specific) are set per customer record so each invoice inherits the right cycle without manual override.
Can the PDF invoice be branded with our company logo plus terms?
+
Yes. Branding pulls the logo, footer terms, color palette, plus contact block from the company profile automatically. Different branding can be applied per business category if your operation runs multiple service lines under different brand identities. The PDF is print-ready out of the system, no external design step required.
How long does Invoices and Quotes take to deploy?
+
Most deployments run weeks, not months. Phase one configures the quote plus invoice templates, tax rules, plus approval workflows. Phase two connects line item sources from Work Orders, Inventory Control, plus Project Templates. Migration of open AR balances is the third phase. Ikhana walks billing staff through every screen on demand. Controllers typically see the first re-entry-free invoice cycle inside the first month.
Allison Woolbert, principal of Phoenix Consultants Group
Allison Woolbert
Principal, Phoenix Consultants Group

Phoenix Consultants Group founded 1995. Allison's experience in software development predates that. 500+ applications built across small businesses, Fortune 500 firms, plus government contractors. Every call answered, with most issues on PCG-built software resolved the same day.

phxconsultants.com fireflightdata.com LinkedIn

Phoenix Consultants Group founded 1995. FireFlight Data Systems is the proprietary modular platform hosted by PCG. Page prepared May 2026.

From Estimate to Invoice to Receipt:
Everything You Need in One Interface

Simplify billing from first quote to final payment: with clear records, line-item detail, and a unified system that supports both service and sales.

Last updated: May 2026

Inventory Turnover Reporting: Which SKUs Earn Their Shelf Space plus Which Ones Tie Up Your Cash

Inventory Turnover Reporting is the FireFlight app that calculates turnover ratios by SKU, category, plus location. High-turn winners surface alongside stagnant stock dragging working capital. Monthly, quarterly, or custom date ranges. Standard costing or real-time valuation. Exports built for purchasing plus finance teams. Direct connection to reorder plus safety stock planning.

Can FireFlight calculate inventory turnover ratios by SKU, category, plus location with charts purchasing plus finance can actually use? Yes. Inventory Turnover Reporting tracks turnover ratios across SKUs, categories, plus locations. High-turn versus stagnant items surface in visual dashboards with bar charts plus trendlines. Monthly, quarterly, or custom date ranges. Works with standard costing or real-time valuation. Exports built for purchasing plus finance teams. Deployment runs weeks, not months.

FireFlight Inventory Turnover Reporting screen showing turnover ratio dashboards with high-turn winners, stagnant stock indicators, plus trendline charts by SKU plus category

See how a 9,400-SKU catalog gets ranked by turnover ratio, top movers plus dead stock surface in seconds, plus the purchasing director plus CFO leave the meeting with the same numbers. Live demo or a direct call.

Request a Demo Contact Us

Why does the same warehouse hold stock that turns 12 times a year next to stock that has not moved in 18 months?

In 2026, most operations buy the way they have always bought. The reorder list runs on a fixed reorder point plus a fixed quantity per SKU. Nobody looks at whether the SKU actually earned its shelf space last quarter. Fast movers reorder on time. Slow movers also reorder on time, even when the existing stock has been sitting at the back of the warehouse for a year. The reorder system works flawlessly at making sure the inventory keeps growing.

The cost is working capital tied up in dead inventory. A 9,400-SKU catalog can carry millions in stock where the slowest 20% has not moved in over 12 months. That cash cannot pay vendors. It cannot fund growth. It cannot earn a return. Meanwhile the fast movers occasionally stock out because the safety stock formula treats them the same as the slow movers, plus the team scrambles to reorder under pressure. Procurement spends its time fighting fires that better data would have prevented.

Inventory Turnover Reporting fixes the data side of the problem. The turnover ratio (cost of goods sold divided by average inventory value) calculates automatically for every SKU, category, plus location. High-turn winners surface immediately on the dashboard. Stagnant stock that has not moved in the configured threshold flags for review. The purchasing director gets a ranked list of candidates to discontinue, reduce, or relocate. CFOs receive a working-capital impact estimate for each decision. Reorder rules plus safety stock levels then get tuned against actual movement.

How does the turnover engine handle standard costing plus real-time valuation in the same calculation?

Turnover ratio math depends on the cost of goods sold plus the average inventory value, both expressed in money. The choice of valuation method changes the value side of that equation. A business running standard costing assigns a fixed unit cost per SKU set quarterly or annually. A business running real-time valuation uses FIFO, LIFO, or Weighted Average from Stock Valuation as the live unit cost. Turnover reporting reads either source automatically based on what the controller has configured for each SKU.

The same engine handles mixed environments. Some SKUs may run standard costing for budgeting purposes while raw material commodities run real-time Weighted Average to track market shifts. The turnover report respects each SKU's cost method when calculating the ratio. The output is a single comparable turnover metric across the catalog even when different SKUs use different costing approaches underneath. Purchasing plus finance see one ranked list rather than two parallel views that need reconciling at quarter-end.

Visualization makes the analysis actionable. Bar charts rank SKUs or categories by turnover. Trendlines show how turnover for a specific item has shifted over the last 12 months. Filters cut the view by vendor (which vendor's products move fastest), by warehouse (which site is sitting on dead stock), by classification (where slow-moving inventory concentrates by category), or by movement type. The result is a quarterly review meeting where everyone is looking at the same data plus the same chart, not arguing about whose spreadsheet is right.

What apps does Inventory Turnover Reporting connect to inside FireFlight?

Bar Charts Trendlines CSV plus PDF Export

Turnover data shapes purchasing decisions. We treat it that way.

Reporting data lives in encrypted storage hosted by PCG. Role-based access separates purchasing staff who read the turnover charts from controllers who reconcile against the financial books plus regional managers who get their own scoped view. Sensitive cost data can be restricted at the user level.

Every report run, every export, plus every filter applied is logged with user identity, timestamp, plus the date range queried. The export packet carries a watermark with the export date plus the underlying parameters, so the working paper landing in a quarterly review meeting can be traced back to its exact source query without ambiguity.

Ikhana, the FireFlight on-screen tutor character
On-Screen Tutor

Ikhana shows your team how to run a turnover report, filter by category, plus export the chart for the next quarterly review.

Every field, every filter, every chart option is explained the moment somebody asks. New purchasing analysts run their first dead-stock report the same week they start. No training queue. No tickets to IT.

Learn more about Ikhana

What does Inventory Turnover Reporting give your purchasing plus finance teams?

  • Turnover ratio tracked by SKU, category, or location. One comparable metric ranks the catalog regardless of which costing method each SKU uses underneath.
  • High-turn versus stagnant items highlighted on every dashboard. Top movers plus dead stock surface immediately instead of getting buried in the catalog list.
  • Monthly, quarterly, or custom date ranges. Match the report period to the quarterly review, fiscal close, or seasonal analysis window your team needs.
  • Visual dashboards with bar charts plus trendlines. The chart that lands in the executive review tells the story without a five-page narrative attached.
  • Exportable reports formatted for purchasing plus finance teams. CSV for analytical work, PDF for the formal review packet, plus structured exports for downstream BI.
  • Direct connection to reorder plus safety stock planning. Fast-moving SKUs get tighter reorder triggers; slow movers can be pulled from the auto-reorder list entirely.
  • Filters for vendor, warehouse, classification, or movement type. Slice the analysis by whichever cut the team needs in the moment.
  • Works with standard costing or real-time valuation. Each SKU's chosen cost method feeds the turnover calculation without any reconciliation between models.
"We used turnover trends to cut 22% of slow-moving SKUs, freeing up both space plus cash."
Director of PurchasingNational Retail Chain

31 years of operational software, with AI reporting built in for 2026.

Phoenix Consultants Group has built custom operational software since 1995. Inventory Turnover Reporting is one app inside the FireFlight platform, the same platform running fleet fueling for municipal operators, physician credentialing for staffing firms, plus airport ground equipment management for aviation services.

The AI layer added in 2026 means a CFO can query Inventory Turnover Reporting in plain English. "Show me every SKU with a turnover ratio below 1.5 in the last two quarters, grouped by warehouse plus by vendor, with the working capital tied up in each." The system answers from live data. No report request to IT. No waiting.

What changes operationally after Inventory Turnover Reporting goes live?

  • Dead stock stops accumulating without being noticed. Stagnant items flag every quarter for review, plus the purchasing team has a ranked list ready before each meeting.
  • Working capital gets freed up. Slow-moving SKUs identified through turnover analysis can be discontinued, marked down, or relocated to lower-cost storage.
  • Reorder rules tighten on winners. The fast-turn SKUs that occasionally stock out get tighter triggers plus more responsive safety stock formulas.
  • Quarterly reviews become decision meetings, not data-cleaning meetings. Purchasing plus finance arrive with the same numbers.
  • Vendor negotiations get grounded in data. Procurement walks into the next vendor meeting with the turnover history of that vendor's catalog in hand.

Frequently Asked Questions

How is Inventory Turnover Reporting different from Custom Reporting?
+
Custom Reporting is the generic reporting engine that builds any report from any data in the platform. Inventory Turnover Reporting is a specialized app with the turnover calculations, the high-turn versus stagnant logic, plus the visualization patterns already built. A controller could rebuild similar reports in Custom Reporting from scratch with weeks of effort. The Turnover Reporting app delivers the same analysis on day one with the cost-method handling, filter set, plus chart templates already tuned for purchasing plus finance workflows.
How is turnover ratio calculated?
+
The standard formula is cost of goods sold divided by average inventory value over the same period. The engine pulls COGS from completed shipments plus consumption events. Average inventory value pulls from the SKU's configured cost method (standard costing or real-time Stock Valuation). The result is a ratio: a SKU with turnover of 6 cycles through its average inventory six times in the chosen period. The interpretation depends on the industry, the product category, plus the specific business model, so the dashboard shows raw ratios plus relative ranking instead of an absolute pass-fail threshold.
Can the same report mix SKUs on standard costing with SKUs on real-time valuation?
+
Yes. Each SKU's cost method is read from its own configuration record. Some businesses run standard costing on finished goods plus real-time Weighted Average on raw material commodities. The turnover engine respects each SKU's setup when calculating its ratio. The output ranks all SKUs on one comparable scale regardless of which costing method drove the underlying value. Purchasing plus finance see a single consistent view without anyone having to reconcile between models.
What counts as a stagnant SKU?
+
The threshold is configurable per business. A common starting point is any SKU with a turnover ratio below 1.0 over the last 12 months, meaning the average inventory turned over less than once in a year. Some businesses set the threshold lower (0.5) for niche specialty stock plus higher (3.0) for fast-moving consumer goods. The dashboard flags SKUs against the threshold automatically. The purchasing director can override or refine the threshold by category to match the realistic expectation for each product class.
How does turnover data feed reorder plus safety stock decisions?
+
High-turn SKUs benefit from tighter reorder points plus more responsive safety stock formulas. Low-turn SKUs may benefit from being removed from the auto-reorder list entirely or moved to a manual purchasing review. The Turnover Reporting app surfaces the candidates. Reorder rule updates happen in the relevant inventory or procurement workflows, with the turnover data as the supporting evidence for the change. The audit trail captures every reorder rule change with its source rationale.
Can we filter turnover by vendor for negotiation prep?
+
Yes. The vendor filter cuts the turnover report to show only SKUs sourced from a specific supplier. Procurement can see which of that vendor's products move fastest, which lag, plus the working capital implications of the current order pattern. The chart goes into the negotiation packet directly. Vendors selling slow-moving SKUs can be challenged on pricing, terms, or SKU rationalization. Vendors with fast-moving SKUs can be approached for volume discounts.
How long does Inventory Turnover Reporting take to deploy?
+
Most deployments run weeks, not months. Phase one defines the stagnant-stock threshold, the standard reporting periods, plus the permission roles with the purchasing director plus the controller. Phase two configures the connections to Stock Valuation plus Inventory Control for live cost plus quantity feeds. Phase three loads the historical transaction data needed for the first 12 months of trendlines. Ikhana walks purchasing plus finance staff through every screen on demand. Purchasing directors typically see their first actionable dead-stock report inside the first month of go-live.
Allison Woolbert, principal of Phoenix Consultants Group
Allison Woolbert
Principal, Phoenix Consultants Group

Phoenix Consultants Group founded 1995. Allison's experience in software development predates that. 500+ applications built across small businesses, Fortune 500 firms, plus government contractors. Every call answered, with most issues on PCG-built software resolved the same day.

phxconsultants.com fireflightdata.com LinkedIn

Phoenix Consultants Group founded 1995. FireFlight Data Systems is the proprietary modular platform hosted by PCG. Page prepared May 2026.

Turn Inventory Data Into Strategic Movement

Spot slow movers, double down on high performers, and align your inventory plan with real-world demand, all from one clear dashboard.

Last updated: May 2026

Inventory Control: The Master Ledger Every Other FireFlight App Reads From

Inventory Control is the FireFlight app at the center of the platform. The live ledger of every SKU at every site, with status flags (Available, Reserved, Damaged, In Transit, Obsolete) that go beyond a single quantity number. Freeze, lock, plus reconcile when the floor reality calls for it. Full audit trail on every transaction.

Can FireFlight maintain a real-time inventory ledger across all sites with status flags beyond just quantity-on-hand? Yes. Inventory Control delivers centralized live tracking across every site, location, plus warehouse in one ledger. Status flags separate Available stock from Reserved, Damaged, In Transit, plus Obsolete. Quantity updates post in real time from incoming plus outgoing orders. Freeze, lock, plus reconciliation tools. Full audit trail on every transaction. Deployment runs weeks, not months.

FireFlight Inventory Control screen showing centralized inventory ledger with status flags, location-by-location breakdown, plus filters for product, vendor, plus status across multiple sites

See how the master inventory view shows what is available, what is reserved against open orders, what sits in damaged status awaiting disposition, plus what is in transit between sites in one screen. Live demo or a direct call.

Request a Demo Contact Us

Why does your "quantity on hand" number lie to procurement, to sales, plus to the auditor all at the same time?

In 2026, most inventory systems carry one quantity number per SKU per location. That single figure has to mean different things to different teams across the business. Procurement reads it as available stock. Sales reads it as committable stock to promise to a customer. The auditor reads it as on-hand stock to validate the balance sheet. The number cannot be all three at once, because Reserved units, Damaged units, plus In-Transit units behave differently from genuinely Available units. The system collapses them all into one figure plus everybody works from the wrong picture.

The cost shows up as overcommitments plus stockouts that should never have happened. A salesperson promises 200 units from a SKU showing 240 on hand, not knowing 80 are reserved against a previous order plus 35 are damaged stock awaiting vendor pickup. The order ships short. Procurement sees 240 on hand plus declines to reorder, then the next customer order arrives plus there is nothing to fulfill from. The auditor at quarter-end finds inventory the books say is worth full value but physically sits in the Damaged corner of the warehouse, plus the controller has to explain why the write-down was not booked earlier.

Inventory Control fixes this by treating status as first-class data, not a comment field. Every unit of inventory carries a status flag: Available, Reserved, Damaged, In Transit, plus Obsolete. The dashboard shows each status separately so procurement reads Available, sales reads Available minus Reserved, plus the controller reads the full breakdown for financial reporting. The same underlying ledger answers different questions cleanly for different teams. No collapsed single number lying to everybody.

How does freeze, lock, plus reconciliation work during a count without halting operations?

Freeze locks a SKU, a location, or a category against any further transactions for the duration of a physical count, an investigation, or a controlled adjustment. While the freeze is active, the ledger remembers exactly what the system thought was there. Counters can do their work without races against live orders. When the count completes, the reconciliation tool compares system quantities against counted quantities, flags variances for review, plus posts the adjustments only after the controller approves them. The freeze releases when the reconciliation closes.

Lock differs from freeze in scope. Lock applies to a single transaction record (say, an in-progress receipt or a half-completed transfer) to prevent two users from editing it simultaneously. Optimistic locking lets multiple users read the record at the same time but prevents conflicting writes. The user whose change posts second sees a conflict warning plus the chance to merge or refresh before retrying. The ledger never loses an event to a race condition between two well-meaning users.

Reconciliation tools cover the rest of the variance resolution workflow. The bulk-adjustment screen handles the post-count corrections with reason codes plus authorized approvers. The investigation queue holds variances that require deeper review before adjustment posts. Every adjustment runs through the audit trail with its source (count session, investigation, manual correction) plus the linked Physical Inventory record when applicable. The whole reconciliation cycle stays inside Inventory Control instead of fragmenting across separate spreadsheets.

Status Flags Real-Time Sync Audit-Ready

An inventory ledger that powers everything else has to be defensible. We treat it that way.

Inventory data lives in encrypted storage hosted by PCG. Role-based access separates floor staff who post transactions from supervisors who approve adjustments plus controllers who reconcile against the financial books. Sensitive SKUs (controlled goods, high-value components, regulated materials) can be restricted to specific user groups.

Every quantity change carries authenticated user identity, timestamp, plus the source transaction. Freeze plus lock controls prevent race conditions during counts plus controlled operations. The full audit trail feeds Inventory Audit Trail for the complete change history any external auditor can read directly under time-bound credentials.

Ikhana, the FireFlight on-screen tutor character
On-Screen Tutor

Ikhana shows your team how to read the status breakdown, set a freeze, plus reconcile a count session inside the live ledger.

Every field, every status flag, every reconciliation prompt is explained the moment somebody asks. New inventory staff post their first clean transaction the same week they start. No training queue. No tickets to IT.

Learn more about Ikhana

What does Inventory Control give your operations plus finance teams?

  • Centralized inventory tracking across every site plus location. One ledger, many warehouses, one source of truth for current stock state.
  • Status flags beyond simple quantity-on-hand: Available, Reserved, Damaged, In Transit, plus Obsolete. The number means what the team thinks it means.
  • Real-time quantity updates from incoming plus outgoing orders. The ledger reflects what just happened on the floor, not what was true at the last sync.
  • Inventory classification by type, category, plus unit of measure. The taxonomy from Item Categorization feeds the ledger structure across every site.
  • Low stock plus overstock alerts. Notifications fire on configurable thresholds so the procurement team sees risk before it becomes a stockout or a writedown.
  • Inventory history plus movement logs visible on every SKU record. Where did this stock come from, where did it go, plus when did each move happen.
  • Freeze, lock, plus reconciliation tools for counts plus controlled adjustments. Race conditions get prevented at the data layer rather than patched after the fact.
  • Flexible filters plus data views by location, product, vendor, or status. The auditor sees what they need plus procurement sees what they need from the same data.
  • Full audit trail for every inventory transaction. Inventory Audit Trail reads the same data with the four W's (what, when, who, why) attached.
  • Direct connection to Custom Reporting plus ad-hoc analysis system-wide. Every other FireFlight inventory app reads from this ledger as the source of truth.
"We improved our inventory accuracy by 97% within the first month."
Operations ManagerMid-size Manufacturer

31 years of operational software, with AI reporting built in for 2026.

Phoenix Consultants Group has built custom operational software since 1995. Inventory Control is one app inside the FireFlight platform, the same platform running fleet fueling for municipal operators, physician credentialing for staffing firms, plus airport ground equipment management for aviation services.

The AI layer added in 2026 means an operations director can query Inventory Control in plain English. "Show me every SKU where the Available status dropped below safety stock this week while Reserved units exceed 30 percent of total on-hand, grouped by warehouse." The system answers from live data. No report request to IT. No waiting.

What changes operationally after Inventory Control goes live?

  • Sales stops overcommitting based on collapsed numbers. The committable figure is Available minus Reserved, calculated by the system, not estimated by the rep.
  • Procurement reorders against the right signal. Low stock alerts fire on Available quantity, not on a total that includes damaged or obsolete inventory.
  • Damaged plus obsolete stock stops hiding inside the master figure. Each status carries its own quantity, surfacing write-down candidates earlier.
  • Counts run cleanly without halting the warehouse. The freeze tool locks the SKUs being counted while the rest of the operation keeps moving.
  • Every other inventory app gets a trustworthy data feed. Stock Valuation, Stock Transfers, Physical Inventory, plus the rest read from one consistent ledger.

Frequently Asked Questions

What status flags does Inventory Control support, plus why do they matter?
+
The core set: Available (ready to ship or use), Reserved (committed to an open order but not yet shipped), Damaged (physically present but not sellable until disposition), In Transit (moving between sites under a transfer record), plus Obsolete (no longer carried but still on the floor pending disposition). Custom statuses can be added per business need. Status matters because the same SKU at the same location may have units in three different statuses, plus collapsing them into one number is the most common source of overcommitments, stockouts, plus uncaught write-downs.
How does Inventory Control relate to the other inventory apps in FireFlight?
+
Inventory Control is the master ledger for current stock state. The other inventory apps each handle a specific aspect: Real-Time Stock Deduction is the event engine that updates the ledger. Stock Valuation tracks dollar value under FIFO, LIFO, or Weighted Average. Physical Inventory runs the periodic count plus reconciliation. Inventory Audit Trail preserves the complete change history. Inventory Turnover Reporting analyzes velocity. Stock Transfers handles inter-site movement. Each reads from or writes to Inventory Control as its source of truth.
How real-time is the inventory ledger?
+
Updates post the moment the triggering event happens, not on a nightly batch cycle. A barcode scan during a pick deducts inventory immediately. A receipt posting from the dock increments immediately. A transfer leaving the origin warehouse decrements at handoff. The ledger that any user reads thirty seconds later reflects what actually happened on the floor thirty seconds ago. Real-Time Stock Deduction is the engine that drives this; Inventory Control is the ledger that holds the result.
What is the difference between freeze plus lock?
+
Freeze applies to a SKU, location, or category for the duration of a controlled operation like a physical count or an investigation. While the freeze is active, transactions against the affected inventory are blocked or queued until the operation closes. Lock applies to a single transaction record to prevent two users from editing it at the same instant. Lock is a concurrency-control feature; freeze is an operational-control feature. Both are recorded in the audit trail.
How do low stock plus overstock alerts work?
+
Each SKU at each location can carry its own low-stock threshold plus overstock ceiling. Low-stock alerts fire when Available quantity drops below the threshold. Overstock alerts fire when total on-hand exceeds the ceiling, surfacing slow-moving SKUs that have accumulated beyond expected demand. Alerts route by configurable rules to the right team member through email, dashboard, or both. Thresholds can be tuned over time using turnover data from Inventory Turnover Reporting.
Can the ledger handle the same SKU stocked at many sites?
+
Yes. Each SKU exists once in the master catalog plus carries an inventory record at each location where it is stocked. A single SKU can show 240 units at the East Coast warehouse, 180 at the Midwest hub, plus 320 at the West Coast distribution center, with status breakdowns separate for each location. Multi-Warehouse Support coordinates the network-level view; Inventory Control provides the per-site detail underneath.
How long does Inventory Control take to deploy?
+
Most deployments run weeks, not months. Phase one defines the location structure, the status flag set, plus the permission roles with the operations lead plus controller. The structure stays editable later. Phase two migrates the existing SKU catalog plus current quantities from the prior system into the new ledger. Phase three runs a parallel period where the new ledger plus the old system both receive transactions before the final cutover. Ikhana walks operations plus finance staff through every screen on demand. Operations leads typically see their first clean cross-site inventory view inside the first month of go-live.
Allison Woolbert, principal of Phoenix Consultants Group
Allison Woolbert
Principal, Phoenix Consultants Group

Phoenix Consultants Group founded 1995. Allison's experience in software development predates that. 500+ applications built across small businesses, Fortune 500 firms, plus government contractors. Every call answered, with most issues on PCG-built software resolved the same day.

phxconsultants.com fireflightdata.com LinkedIn

Phoenix Consultants Group founded 1995. FireFlight Data Systems is the proprietary modular platform hosted by PCG. Page prepared May 2026.

Tailored Inventory Management That Scales With Your Needs

Manage inventory with speed, accuracy, and full system alignment: so every unit, order, and update is exactly where it should be.

Fixed Asset Management App: Total Lifecycle Oversight for Capital Investments | FireFlight
Last updated: April 2026

Fixed Asset Management: Total Lifecycle Oversight for Every Capital Investment

Centralized fixed asset register for machinery, equipment, tools, and facilities. Automated depreciation calculations. Full transfer history and lifecycle phase tracking. Linked to maintenance schedules, warranties, and audit logs.

FireFlight's Fixed Asset Management app tracks every capital asset from acquisition through disposal in a single register. Purchase cost, supplier, depreciation schedule, warranty status, location, and lifecycle phase all on the same record. Depreciation calculations run automatically. Transfers and renumbering events log as auditable history. Deployments complete in weeks, not months.
FireFlight Fixed Asset Management app showing capital asset register with depreciation tracking and lifecycle status

In 2026, organizations managing fixed assets in spreadsheets are carrying the same four risks simultaneously: depreciation calculations that may be wrong because the spreadsheet has not been updated, assets that appear on the register but were disposed of months ago, assets that are in use but were never formally added, and transfer history that lives in email threads nobody can locate when an auditor asks. FireFlight's Fixed Asset Management app closes each of those gaps by connecting the register to the events that change it rather than requiring manual updates as a separate administrative task.

Schedule your free consultation

How does FireFlight handle depreciation tracking and automated calculations?

Depreciation schedules configure per asset in FireFlight with the method, useful life, and residual value defined at registration. Calculations run automatically against the schedule without manual spreadsheet maintenance. Finance teams see current book value, accumulated depreciation, and remaining useful life from the asset record without running a separate calculation or importing data from an accounting tool. When an asset's depreciation parameters change, the updated schedule applies going forward and the change logs in the asset history.

For organizations managing hundreds of capital assets across multiple depreciation methods, the manual spreadsheet approach produces errors in proportion to the number of assets. A single incorrect entry in a depreciation formula affects every period that follows. FireFlight removes that error source by running the calculation from the parameters rather than from a formula that someone entered and no one has reviewed since.

PCG has been building fixed asset management systems for manufacturing, industrial, and compliance-driven organizations since 1995. The depreciation accuracy problem is consistent across every organization that manages a significant capital asset base in spreadsheets: the calculations drift over time as assets are added, transferred, and retired without the spreadsheet being kept fully current.

How does FireFlight track asset transfers and renumbering events?

Asset location assignments and transfers log as history events in FireFlight rather than overwriting the previous record. When an asset moves between departments, buildings, or sites, the transfer logs with a timestamp and the user who made the change. The current location and the full transfer history are both accessible from the asset record. Finance and operations teams see the same location data without reconciling separate records maintained by each department.

Asset number changes and renumbering events also log as auditable history. When an asset is renumbered, the previous number, the new number, the date, and the responsible user all record against the asset. Audit requests that reference old asset numbers are answerable from the current record without cross-referencing historical spreadsheets to find where the original number went.

What poor fixed asset records cost organizations at audit time: Assets on the register that were disposed of years ago, still showing book value that affects the balance sheet. Assets in active use that were never capitalized because the acquisition was handled informally. Transfer history that cannot be produced because it was tracked in email and the relevant people are no longer with the organization. Depreciation figures that do not agree with the accounting system because they were calculated in a separate spreadsheet that diverged at some point nobody can identify.

Each of those problems shows up at audit time as a finding that requires explanation and remediation. FireFlight's Fixed Asset Management app prevents them by making the register authoritative: acquisitions register at purchase, disposals update the lifecycle status, transfers log as they happen, and depreciation runs from the parameters rather than from a formula someone entered manually. PCG has been building fixed asset management systems for regulated and compliance-driven organizations for over 30 years. The register that stays current is the one connected to the events that change it.

Ikhana on-screen guide
Meet Ikhana

Your Personal Guide on Every Page

From the first click to the final step, Ikhana, your on-screen tutor, shows you how it all works. Every field, every button, every page explained with clarity, right where you need it.

In the Fixed Asset Management app, Ikhana walks finance teams, facilities managers, and operations staff through asset registration, depreciation schedule setup, transfer logging, and disposal processing. New team members manage capital assets accurately from their first week without a dedicated training engagement for each workflow.

Learn more about Ikhana

What does the Fixed Asset Management app actually track?

  • Centralized fixed asset register for all capital equipment and tools: Every capital asset in a single register: machinery, vehicles, facility equipment, IT hardware, and tools. Each asset carries its full metadata set from registration through disposal. The register is the authoritative source for every asset rather than a summary of data maintained in separate departmental spreadsheets.
  • Depreciation tracking with automated calculations: Depreciation schedules configure per asset with method, useful life, and residual value. Calculations run automatically without manual maintenance. Finance sees current book value, accumulated depreciation, and remaining useful life from the asset record without importing data from a separate calculation tool.
  • Location assignments and department transfers with full history: Every location assignment and transfer logs as a history event with timestamp and user attribution. Current location and full transfer history are both accessible from the same record. Finance and operations see the same location data without reconciling separate departmental records.
  • Lifecycle phase tagging from acquisition through disposal: Assets carry configurable lifecycle phase tags: Active, Under Repair, In Reserve, Retired, Disposed. Phase transitions log as auditable events. Assets at each stage are visible from the register dashboard without a custom filter for each query.
  • Asset number history and renumbering event logs: Every numbering change logs with the previous number, the new number, the date, and the responsible user. Old asset numbers trace to the current record. Audit requests that reference historical numbers are answerable without cross-referencing separate records.
  • Linked documents, warranties, and manuals: Purchase orders, warranty documents, equipment manuals, compliance certifications, and disposal records attach directly to the asset. Audit requests, insurance claims, and regulatory inspections are answered from the attached documentation without searching filing systems or shared drives.
  • Integration with PM schedules and asset audit logs: Preventive maintenance schedules attach to capital assets and generate work orders when service is due. PM records connect to the asset's service history so finance sees the maintenance investment alongside the depreciation schedule and current book value from the same record.

What PCG learned building fixed asset management systems across 31 years of regulated and industrial environments: The fixed asset register that stays accurate is not the one with the most fields or the most sophisticated depreciation engine. It is the one that is updated at the point of each event rather than in a periodic reconciliation cycle that accumulates errors between runs.

FireFlight's Fixed Asset Management app makes the update fast enough to happen when the event occurs. An acquisition registers when the purchase is processed. A transfer logs when the move happens. A disposal updates the lifecycle status when the decision is made. The register reflects the actual asset base because maintaining it is embedded in the workflows rather than added on top of them as a separate step. Deployments complete in weeks, not months, and existing fixed asset data migrates from spreadsheets or accounting systems as part of the process.

"Before, our assets were scattered across spreadsheets. Now we know where every capital investment is, what it is worth today, and how it has been maintained."
Finance LeadTooling and Manufacturing Firm

What changes after deploying Fixed Asset Management?

  • Depreciation figures are accurate and current. Calculations run from the configured parameters rather than from manually maintained spreadsheet formulas. Finance teams work from book values they can rely on rather than verify.
  • Audits are answered from the register rather than prepared for the register. The documentation, transfer history, depreciation schedule, and disposal records are all in the system record when the auditor asks rather than assembled in the days before.
  • Finance and operations work from the same location and lifecycle data. Departmental transfers update the register when they happen rather than appearing in finance records at the next reconciliation cycle.
  • Disposed assets leave the register when they are disposed. The balance sheet reflects the current active asset base rather than including equipment that was written off operationally but never updated in the register.
  • Maintenance investment is visible alongside financial performance. PM records link to the depreciation schedule so the total cost of ownership view includes both the capital value and the maintenance cost against each asset.

Questions about FireFlight Fixed Asset Management

What types of assets does FireFlight Fixed Asset Management track?
+
FireFlight's Fixed Asset Management app tracks all capital equipment and tools: machinery, vehicles, facility equipment, IT hardware, and any other capital investment that carries a depreciation schedule. Each asset registers in the fixed asset register with purchase date, supplier, cost, depreciation method, warranty status, location, and current lifecycle phase.
How does FireFlight handle depreciation tracking and calculations?
+
Depreciation schedules configure per asset in FireFlight with the method, useful life, and residual value defined at registration. Depreciation calculations run automatically against the schedule without manual spreadsheet maintenance. Finance teams see current book value, accumulated depreciation, and remaining useful life from the asset record without running a separate calculation or importing data from a separate tool.
How does FireFlight track asset transfers and department assignments?
+
Asset location assignments and transfers log as history events in FireFlight rather than overwriting the previous record. When an asset moves between departments, buildings, or sites, the transfer logs with a timestamp and the user who made the change. The current location and the full transfer history are both accessible from the asset record. Finance and operations see the same location data without reconciling separate records.
Does FireFlight support asset number changes and historical renumbering logs?
+
Yes. Asset number changes and renumbering events log against the asset record in FireFlight with the previous number, the new number, the date of the change, and the user who made it. The full numbering history is traceable from the record. Audit requests that reference old asset numbers are answerable from the current record without cross-referencing historical spreadsheets.
How does Fixed Asset Management connect to maintenance scheduling and PM records?
+
Fixed Asset Management connects directly to Maintenance Scheduling in FireFlight. Preventive maintenance schedules attach to capital assets and generate work orders automatically when service is due. PM records link to the asset's service history so finance and operations both see the maintenance investment alongside the depreciation schedule and current book value.
Can we attach documents, warranties, and manuals to fixed asset records in FireFlight?
+
Yes. Purchase orders, warranty documents, equipment manuals, compliance certifications, and disposal records all attach directly to the asset record in FireFlight. Audit requests, insurance claims, and regulatory inspections are answered from the attached documentation without searching shared drives or physical filing systems.
How long does it take to deploy Fixed Asset Management in FireFlight?
+
Most Fixed Asset Management deployments complete in weeks, not months. PCG configures the fixed asset register structure, depreciation schedule parameters, lifecycle phase definitions, and integrations with maintenance scheduling and IT asset records for your specific capital asset base before go-live. Existing fixed asset data migrates from spreadsheets or accounting systems as part of the deployment.

In 2026, a fixed asset register in spreadsheets is a depreciation error, an audit finding, and a compliance gap all waiting to happen. FireFlight's Fixed Asset Management app keeps the register current because every event that changes an asset connects directly to the record that needs to reflect it. Deployments complete in weeks, not months.

Schedule your free consultation

Allison Woolbert
Allison Woolbert
Principal, Phoenix Consultants Group  |  Developer, FireFlight Data Systems

PCG founded 1995. 500+ applications built across 31 years, roughly one-third in regulated environments where software failure carries direct operational and compliance consequences. FireFlight is the platform built from that body of work. When you contact PCG, Allison is the person who answers.

phxconsultants.com LinkedIn

FireFlight Data Systems is a product of Phoenix Consultants Group. PCG founded 1995. All system configurations are custom-built for each deployment. Implementation timelines, module availability, and integration scope vary by organization. Contact PCG directly to discuss requirements specific to your operation.

Protect Your Investments and Maximize Asset Longevity

From purchase to retirement, manage your physical assets with accuracy; ensuring compliance, accountability, and cost efficiency every step of the way.

Last updated: May 2026

Goods Receipt Management: know what arrived and what did not

Your receiving process generates data your procurement and inventory teams need the moment a delivery is closed. This app ties every receipt directly to its purchase order, flags discrepancies before they become disputes, and keeps your receiving logs auditable by vendor, date, or PO number.

Can FireFlight track partial shipments and receiving discrepancies against open purchase orders?
Yes. Goods Receipt Management auto-generates a receiving document from every active PO, lets your team update quantities across multiple sessions, and captures unexpected items or overages in the same record. Every change is timestamped, linked to a vendor, and visible to procurement in real time. Deployments take weeks, not months.
Goods Receipt Management workspace showing delivery logs, PO status, and receiving discrepancies in FireFlight

In 2026, receiving teams are still reconciling paper manifests against spreadsheet PO logs after the fact. That gap is where shortages go unnoticed and billing disputes start. See how this works on a live dataset.

Request a Live Demo Contact Us

Why does receiving break down when volume goes up?

Most receiving failures share a common origin: the person signing for a delivery has no fast way to check what the PO actually said was supposed to arrive. They count what is in front of them, write it on a paper form, and the reconciliation happens later, sometimes days later, when someone in procurement notices the numbers do not match. By then the truck is gone, the vendor has moved on, and proving the discrepancy falls on whoever filed the paperwork.

Partial shipments make this worse in a specific way. If a vendor ships 60 units on Monday and 40 more on Thursday, a paper-based process has two separate receiving records that need to be manually linked back to one PO. The receiving staff at Thursday's dock may not even know the first 60 came in. The PO looks open. The inventory count is wrong. The finance team gets a full invoice for a delivery that has not been fully received yet.

The problem is not the volume. It is that the receiving activity is disconnected from the purchasing record at the moment it matters most, which is while the delivery is happening. When that connection exists in real time, the dock team knows exactly what to expect, can document what actually arrived, and flags anything that does not match before closing the receipt.

How does Goods Receipt Management keep receiving and procurement in sync?

When a purchase order is created in FireFlight, the Goods Receipt app generates a corresponding receiving document automatically. The dock team opens that document, sees the expected items and quantities from the original PO, and records what actually arrived. They can update in one session or across multiple sessions if the shipment is staggered. The system maintains a running received-versus-ordered count per line item so the PO status reflects reality at any moment.

Discrepancies get captured at the point of receipt, not days later during a reconciliation audit. If the vendor ships a substitute item or an overage, the receiving team adds it directly to the record with a note. That note stays attached to the PO, the vendor record, and the resulting inventory adjustment. The next time your procurement team negotiates with that vendor, the exception history is already there.

File attachments and delivery timestamps are included on every receipt. A driver's delivery confirmation, a photo of damaged goods, a packing slip that does not match the order: all of it lives in the same record. Weeks, not months to get this running inside your existing FireFlight environment. There is no separate implementation track for this module.

What apps does Goods Receipt Management connect to?

This module is active inside your FireFlight procurement and inventory environment. It reads from open purchase orders and writes directly to inventory and financial records when a receipt is closed.

QuickBooks Email Notifications Document Storage

Your receiving data stays on your platform

FireFlight is hosted by Phoenix Consultants Group on infrastructure PCG owns and manages. Your receiving logs, vendor discrepancy records, and PO reconciliation history are not stored in a shared SaaS environment alongside competitors or unknown third parties. PCG has controlled its own hosting since 1995.

Access permissions by role mean your dock team sees what they need for receiving, your procurement team sees the full PO history, and your finance team sees the closed-receipt data that feeds billing. No one sees what they should not. Every action in the receiving record carries a user stamp and a timestamp.

What does Goods Receipt Management give your team?

  • Auto-generated receiving documents from every open PO. The document exists before the truck arrives. Your team confirms or corrects, they do not build from scratch.
  • Real-time quantity updates across multiple receiving sessions. Partial shipments stay linked to one PO record. The running total is always current.
  • Discrepancy capture at the dock, not in a spreadsheet two days later. Unexpected items, overages, plus any substitutions get documented the moment they are noticed.
  • File attachments and delivery timestamps on every receipt. Packing slips, delivery photos, and driver confirmations live inside the record, not in someone's email inbox.
  • Fully auditable receiving logs searchable by vendor or PO. When a dispute arrives weeks after delivery, the complete receiving record is one search away.
  • Direct connection to Returns, Inventory, plus the Financial modules. A closed receipt updates inventory counts and flags billing without a separate data entry step.
  • Role-based access so dock staff, procurement, plus finance each see their relevant view. No shared logins. No one editing records outside their function.
"Our receiving is consistent and traceable now. No more guessing what came in, what is missing, or who signed for it. The logs speak for themselves."
Mira S.Procurement Officer

Ask your receiving data a question. Get an answer in English.

FireFlight's AI reporting layer lets procurement managers and operations leads query live receiving data without writing a report or waiting on IT. In 2026, that means typing a question like "which vendors had receiving discrepancies in the last 90 days" or "show me all partially received orders over 30 days old" and getting the answer directly from your own data.

Phoenix Consultants Group has been building custom software since 1995. The AI layer is not a third-party plugin bolted onto a generic platform. PCG built it into FireFlight specifically for operations teams that need answers from their data without depending on a report that someone else has to build first. The same team that built the software answers the phone when something needs adjusting.

What changes operationally after deploying this app?

  • Receiving discrepancies are documented at the time of delivery, not reconstructed after the fact during a billing dispute.
  • Partial shipments are tracked against one PO record across multiple delivery sessions, so procurement always knows the current received quantity.
  • Inventory counts update when a receipt closes, removing the lag between physical arrival and system availability.
  • Vendor exception history accumulates automatically, giving procurement a factual basis for renegotiating terms with suppliers who consistently ship short or late.
  • Finance can match invoices to closed receipts without chasing down paper records or asking the dock team to reconstruct what arrived two weeks ago.

Frequently Asked Questions

Can Goods Receipt Management handle partial shipments split across multiple delivery dates?
+
Yes. A single receiving document stays open and linked to its originating PO across as many delivery sessions as the shipment requires. Each session updates the running received quantity on that PO line. The procurement team sees a live count at any point, not a final tally only after the last box arrives. When the full order is received, the document closes and triggers the downstream inventory and billing updates.
How does the app document receiving discrepancies so they hold up in a vendor dispute?
+
When a quantity does not match the PO, the receiving team records the actual count and adds a note directly on the document. File attachments for packing slips, photos of damaged goods, or any other supporting documentation attach to the same record. Every entry carries a user stamp and a timestamp. If a dispute comes up weeks later, the complete receiving record is available by vendor name or PO number in one search.
Does the receiving record update inventory automatically when a receipt is closed?
+
Yes. When a receipt closes, the confirmed quantities flow into Inventory Control without a separate data entry step. Your inventory counts reflect what physically arrived, not what was ordered. If a receipt is closed with a partial quantity, the inventory update matches that partial amount and the PO stays open for the remainder. The financial module also sees the closed receipt when matching invoices.
How long does it take to deploy Goods Receipt Management inside our existing FireFlight setup?
+
For teams already running FireFlight for procurement or inventory, adding this module typically takes weeks, not months. PCG configures the receiving document template to match your PO structure, sets role-based access for dock staff versus procurement versus finance, and runs your team through the workflow using Ikhana's on-screen guidance. There is no separate implementation track. The module is built to connect to your existing PO and inventory data from day one.
Can we track receiving performance by vendor over time?
+
Yes. Every receiving record is linked to a vendor. The discrepancy notes, short shipments, overages plus substitutions that accumulate over time become a factual performance history tied to that vendor's record. You can search and filter by vendor across all past receipts. The AI reporting layer in FireFlight also lets procurement managers query that history in plain English, for example asking which vendors had more than two discrepancies in a given period, and get a direct answer from live data.
What happens when a vendor sends an item that was not on the original purchase order?
+
The receiving team can add unexpected items directly to the receipt document with a note explaining the situation. That addition does not alter the original PO. It creates a documented exception that procurement can see immediately and act on, whether that means returning the item, accepting it with a PO amendment, or flagging it for finance to hold payment. The record of what arrived, including the unexpected item, is captured at the time of delivery.
Is this module suitable for operations teams that are not tech-heavy?
+
Yes, and that is by design. The dock team interface shows only what is relevant for the current receipt: the expected items, the quantity fields, the attachment tool, and the close button. Ikhana walks users through each step with on-screen guidance, so no one needs to read documentation before they can do their job. PCG has been building software for operations teams with no dedicated IT staff since 1995. The system is configured to match how your team actually works, not the other way around.
Ikhana interactive tutorial guide
On-Screen Guide

Your team does not need a manual

Ikhana walks every user through the receiving workflow from the moment they open a receipt document. Which fields to fill. What to do when quantities do not match. How to attach a delivery photo. The guidance is there at every step, so a new dock team member is productive the same week they start.

Learn more about Ikhana
Allison Woolbert, Principal of Phoenix Consultants Group
Allison Woolbert
Principal, Phoenix Consultants Group

Allison has been building custom operations and compliance software since before PCG was founded in 1995. Over 31 years and 500+ applications, she has worked with small businesses, Fortune 500 companies, nonprofits, plus government contractors. FireFlight is the platform that grew out of that work: a modular, AI-integrated system that PCG hosts, maintains, plus supports directly.

phxconsultants.com LinkedIn

Phoenix Consultants Group. Founded 1995. FireFlight Data Systems is a proprietary platform developed and hosted by PCG. Page last reviewed May 2026.

Integrated Apps

This app works closely with:

icon-purchase-orders-blue_1080x1080
Purchase Orders
icon-vendor-catalogue-blue_1080x1080
Vendor Catalog Management
icon-supplier-management-blue_1080x1080
Supplier Management
icon-returns-blue_1080x1080
Returns & RMA Processing
icon-ad-hoc-blue_1080x1080
Ad-Hoc Reporting
icon-custom-reporting-blue_1080x1080
Custom Reporting
icon-inventory-control-blue_1080x1080
Inventory Control
icon-procurement_1080x1080
Procurement

Every Delivery Logged. Every Exception Tracked.

Goods Receipt Management streamlines your warehouse or operations team’s interaction with incoming orders. Whether items arrive in partial shipments or with overages, the system makes it easy to document changes and keep records synced with procurement and inventory.

 

Key Features

  Auto-generates receiving document from each PO

  Update received quantities in real-time or over multiple sessions

  Add unexpected items and capture receiving discrepancies

  Maintain running status of partially received orders

  Link notes, file attachments, and delivery timestamps

   Fully auditable receiving logs per vendor or PO

  Seamlessly connects with Returns, Inventory, and Financial modules

Your Personal Guide on Every Page

From the first click to the final step, Ikhana, your on-screen tutor, shows you how it all works. Every field, every button, every page – explained with clarity, just a tap away.

Help Where You Need It - Instantly!

Related Systems

Integrates with the following enterprise environments:

icon-erp-blue_1080x1080
ERP(Enterprise Resource Planning)
icon-supply-management-blue_1080x1080
Supply Chain Management
“Now our receiving is consistent and traceable. No more guessing what came in, what’s missing, or who signed for it. The logs speak for themselves.”
Mira S.
Procurement Officer

Receive with Confidence, Record with Precision

Close the loop between orders and deliveries— with real-time updates, clear documentation, and full accountability at the dock.

Last updated: May 2026

Email Template Manager: One Source of Truth for Every Outbound Message

FireFlight Email Template Manager keeps every system email branded plus accurate, whether it fires automatically from a work order or goes out by hand. One central library. Role-based editing. Merge tags that pull live data at send time in 2026.

Where do your outbound emails actually come from? If different staff are pasting from old drafts, or templates live in five inboxes nobody owns, Email Template Manager replaces that. Every system email pulls from one central library. Role-based editing controls who can change wording. Merge tags pull the right data at send time so the customer sees the correct due date.

FireFlight Email Template Manager interface showing centralized email templates with merge tags and role-based editing in 2026

See how Email Template Manager keeps every customer touchpoint, internal update, plus system alert consistent with your brand and your data. Deployments run in weeks, not months.

Request a Demo Contact Sales

Why do email templates drift out of sync?

Most operations teams in 2026 still maintain their email content in scattered drafts spread across personal inboxes and forgotten folders. One person keeps the credential reminder in a personal inbox. Another saved the invoice cover note as a Word file on a shared drive years ago and forgot about it. Finance has a slightly different version of the same notice. When the legal team changes a disclosure line, one copy gets updated and the others drift.

The problem is that no application owned the email content. Each team treated their templates as private drafts. The same outbound message went out three slightly different ways depending on who pressed send that morning.

Email Template Manager fixes this by holding every template in one central library. Edits go through a role-based approval gate. When the legal disclosure changes, it changes once for every send that uses that template, automatic or manual.

How do merge tags stay accurate at send time?

Every template carries merge tags like [Client Name] or [Due Date]. At the moment the email fires, the platform replaces each tag with the live record value from the database. The customer sees their actual name on their actual due date, not a stale value from a template draft six months old.

Tags pull from any record the template is wired to. A work order email pulls the work order number, the assigned technician, plus the scheduled date from the live record. An invoice email pulls the amount and the terms from the invoice. A certification reminder pulls the credential name and the expiration date from the cert record.

When the source record changes after the template is built, the tag still resolves correctly on the next send. No retyping. No find-and-replace across a folder of saved drafts.

What apps does Email Template Manager connect to?

SMS module link Alerting module link Outgoing Message Logs trace

Role-Based Editing plus Approval Control

Edit permissions sit behind role-based controls. Marketing may revise customer-facing language. Finance owns billing notices. Compliance owns regulatory disclosure. Approval gates keep a draft from going live until the right role signs off, so a typo in legal language cannot reach a customer by accident.

Every template version is recorded. When a regulator asks which exact wording went out last quarter, the answer comes from the version history paired with the Outgoing Message Logs.

Ikhana, the FireFlight on-screen guide
Ikhana On-Page Help

Your guide for every field, every screen

Ikhana walks new users through template creation, merge tag selection, plus the role-based approval workflow without anyone scheduling a training call.

New hires reach productivity in hours instead of weeks. Onboarding stops being a separate project.

Learn more about Ikhana

What does Email Template Manager give your team?

  • A central repository for every system-wide email template. One source of truth, no scattered drafts.
  • Role-based editing plus approval permissions, so a draft change cannot reach customers until the right role signs off.
  • Merge field tags like [Client Name] or [Due Date] that resolve to live record data at the moment the email fires.
  • Integration with the SMS module plus the alerting module. The same content discipline carries across channels.
  • Templates wired to Work Orders, Invoices and Quotes, Notes History, plus Certifications, so the right operational data lands in the right message every time without manual copy.
  • Triggered or manual sending. The library serves automated workflow emails and the one-off message a manager types from a record.
  • Version history on every template, so the exact wording sent on a given date can be reconstructed for an audit.
  • Deployment runs in weeks, not months. Hosting sits on PCG infrastructure.
"We standardized our messaging across teams and cut down email creation time by 80%."
Director of Client CommunicationsRegional Service Network

Ask your template library a question in plain English

Phoenix Consultants Group has built custom database software since 1995. Across 31 years and 500+ applications, roughly a third of that work has involved operational communications plus compliance audit trails for private-sector clients.

FireFlight adds an AI reporting layer on top of your live template library. Type "list every template that still uses the old disclosure paragraph and show how many sends fired from each one last month" and the answer comes back as a working report rather than a ticket assigned to IT. The query happens in weeks, not months of canned-report development.

What changes operationally after deployment?

  • Template drift stops. When legal updates a disclosure line, it updates once for every send that uses that template across the whole platform.
  • Customer-facing emails stop carrying stale data. Merge tags resolve to the current record value at the moment the message fires.
  • Marketing and compliance stop fighting over wording. The approval gate forces the right role to sign off before anything customer-facing goes live.
  • Audit requests for "what exactly did the customer receive on June 14" get answered from the version history plus the Outgoing Message Logs in seconds.
  • New employees learn the library from Ikhana on screen, so onboarding compresses from weeks of shadowing into a few hours of guided work inside the actual app.

Frequently Asked Questions

What is an email template manager and what does this app do?
+
Email Template Manager is a central library for every outbound email your platform sends. Templates carry merge tags that resolve to live data at send time. Role-based editing controls who can change wording. Triggered automation and manual sends both pull from the same library, so the customer experience stays consistent regardless of who hits send.
How do merge tags like [Client Name] actually work?
+
A merge tag inside a template marks a spot where live record data should appear. At the moment the email fires, the platform replaces the tag with the current value from the database. A work order email substitutes the actual work order number and assigned technician. An invoice email substitutes the actual amount due. The customer always sees current data rather than a stale draft.
Who can edit or approve templates?
+
Edit and approval permissions sit behind role-based controls. Marketing may revise customer-facing wording. Finance owns billing notices. Compliance owns regulatory disclosure language. A draft cannot go live until the right role signs off, so a typo in legal language cannot reach a customer by accident.
Does the manager serve both automated and manual emails?
+
Yes. The same library powers triggered emails firing from workflow rules and one-off messages a manager types from a record screen. Either path uses the approved template plus live merge-tag data, so a manually sent message stays as consistent as the automated one.
Can we audit exactly which version of a template went out on a specific date?
+
Yes. Each template carries version history. Paired with the Outgoing Message Logs, the audit returns the exact wording the recipient saw on the date in question, plus the role that approved that version, plus the trigger that fired the send.
How long does Email Template Manager take to deploy?
+
Most deployments complete in weeks, not months. The exact timeline depends on how many existing email templates need to migrate plus how many operational apps are wiring into the library on day one. PCG hosts the platform and answers the phone when something needs adjustment.
Can we query the template library using natural language?
+
Yes. The AI reporting layer lets you type a question like "list every template that mentions the old payment terms language" and receive a working report. The query runs against live template data rather than a canned report, so the answer reflects what the library holds right now.

End the era of scattered email drafts

One library for every outbound message. Role-based editing, live merge-tag data, plus full version history. Deployments measured in weeks, not months. Hosting by PCG with phone support included.

Request a Demo Contact Sales
Allison Woolbert, Principal of Phoenix Consultants Group
Allison Woolbert
Principal, Phoenix Consultants Group

Phoenix Consultants Group has built custom database and compliance software since 1995. Allison's personal software development experience predates that founding. Across 31 years, PCG has delivered 500+ applications spanning customer communications, compliance tracking, plus operational reporting for private-sector clients.

phxconsultants.com fireflightdata.com

Phoenix Consultants Group, founded 1995. FireFlight Data Systems is a proprietary platform hosted by PCG. Page last updated May 2026.

Send Smarter, Say It Right, Stay Consistent.

Empower your team with powerful, reusable email templates.

Last updated: May 2026

Email and SMS Channel Settings: Configure Once, Send Everywhere

FireFlight Email and SMS Channel Settings keeps your platform's outbound messaging credentials in one secure record. Sender identity, SMTP configuration, plus SMS gateway endpoint live in a single source that every workflow draws from in 2026.

Where does your system actually authenticate when it sends a message? Channel Settings holds that configuration in one record per channel. Sender name and address for email. Sender phone number for SMS. SMTP credentials. SMS gateway endpoint, such as Twilio. Every reminder, alert, plus scheduled update fires from this single authenticated profile rather than from scattered server-side settings nobody can find when something breaks.

FireFlight Email and SMS Channel Settings interface showing centralized SMTP plus SMS gateway configuration for authenticated messaging in 2026

See how Channel Settings keeps every email and SMS your platform sends flowing through one authenticated profile. Deployments run in weeks, not months.

Request a Demo Contact Sales

Why does scattered messaging configuration break deliverability?

Most platforms in 2026 still configure outbound messaging in three or four places. One module hard-codes an SMTP server. Another stores SMS credentials in a config file nobody documents. A third uses a sender address that someone set up two years ago and forgot about. When credentials expire or a gateway endpoint changes, the platform starts dropping messages without anyone knowing where to look.

The problem is that no single record owned the messaging channel. Each workflow assumed somebody else handled authentication. Reminders bounced. Customer alerts disappeared into spam. The audit trail showed messages marked sent that recipients never received.

Channel Settings fixes this by holding one configuration record per channel. Email lives in one place. SMS lives in another. Every workflow on the platform draws from these two records rather than from scattered server-side variables.

How does the app handle credential rotation?

Credentials change. SMTP passwords rotate on a quarterly schedule for security teams that follow standard hygiene practices. SMS gateway tokens expire. When that happens, somebody with the right role edits the Channel Settings record once. Every workflow on the platform picks up the new credential on the next send.

Sender identity stays consistent across the rotation. The customer sees the same brand name and reply address before and after the credential changed. The audit trail records which user updated the credential and when. Compliance gets the same paper trail it would expect from any system-of-record change.

Routing endpoints work the same way. When a team moves from one SMS gateway to another, the new endpoint goes in once. Every reminder, every confirmation, plus every workflow alert routes through the new path on the next firing.

SMTP server Twilio gateway Authenticated sender identity

Secure Credential Storage plus Role-Based Edits

Credentials sit behind role-based access. Only the roles authorized to manage outbound messaging can view or edit the Channel Settings record. Passwords and API tokens are stored securely rather than displayed in clear text on the edit screen, so a casual login cannot expose them.

Every change writes to the audit trail with user identity plus timestamp. When deliverability breaks at 2am on a Sunday, the on-call admin sees exactly when the last credential change happened and who made it.

Ikhana, the FireFlight on-screen guide
Ikhana On-Page Help

Your guide for every field, every screen

Ikhana walks new admins through SMTP setup, SMS gateway configuration, plus credential rotation without anyone scheduling a training call.

New hires reach productivity in hours instead of weeks. Onboarding stops being a separate project.

Learn more about Ikhana

What does Channel Settings give your team?

  • A single configuration record for email plus a single record for SMS. One source of truth per channel.
  • Sender name, sender address, plus sender phone number defined once and reused across every workflow that touches a customer.
  • SMTP server settings on the email side. SMS gateway endpoint configuration on the SMS side, including Twilio and other supported providers.
  • Secure authentication plus credential storage. Tokens and passwords stay encrypted at rest.
  • System-wide use across every messaging workflow. Reminders, alerts, confirmations, plus scheduled updates all route through the same record.
  • Easily editable when credentials rotate or routing endpoints change. One edit. Every send picks up the new value.
  • Brand consistency plus message policy compliance enforced at the channel level rather than reinvented per workflow.
  • Deployment runs in weeks, not months. Hosting sits on PCG infrastructure.
"We set it once, and every alert, update, plus reminder flows cleanly. Zero headaches."
Operations CoordinatorMulti-Service Team

Ask your messaging configuration a question in plain English

Phoenix Consultants Group has built custom database software since 1995. Across 31 years and 500+ applications, roughly a third of that work has involved operational messaging plus compliance audit trails for private-sector clients.

FireFlight adds an AI reporting layer on top of your live messaging configuration plus the message logs that depend on it. Type "show every credential change on the SMS channel in the last 60 days and the message volume that fired during each window" and the answer comes back as a working report rather than a ticket assigned to IT. The query happens in weeks, not months of canned-report development.

What changes operationally after deployment?

  • Credential rotation stops being a four-hour project across multiple modules. One record updates. Every workflow picks up the new value on the next send.
  • Sender identity stops drifting. The customer sees the same brand name and reply address on every email regardless of which workflow generated it.
  • When deliverability breaks at midnight, the on-call admin knows where to look. One record, one audit trail, one place to fix.
  • Migrating from one SMS gateway to another stops requiring a sprint. The endpoint change lives in one record.
  • New admins learn channel configuration from Ikhana on screen, so onboarding compresses from weeks of shadowing into a few hours of guided work inside the actual app.

Frequently Asked Questions

What does the Channel Settings app actually configure?
+
Channel Settings holds two configuration records. One for email, one for SMS. The email record covers sender name, sender address, plus the SMTP server settings your platform authenticates against. The SMS record covers sender phone number plus the SMS gateway endpoint. Every outbound message generated by any FireFlight workflow draws from these two records.
Does the app work with Twilio for SMS?
+
Yes. The SMS gateway endpoint configuration supports Twilio plus other SMS providers your operation already uses. Authentication credentials live inside the secure Channel Settings record. Workflows do not need to know which provider sits behind the gateway, so swapping providers does not require rewriting templates or workflows.
How are credentials stored?
+
Passwords and API tokens are stored securely at rest rather than displayed in clear text on the edit screen. Only roles authorized to manage outbound messaging can view or modify the Channel Settings record. Every change writes to an audit trail recording the user identity plus the timestamp of the edit.
What happens when SMTP credentials rotate?
+
An authorized admin edits the Channel Settings record once with the new credential. Every workflow on the platform picks up the new value on the next send. Sender name and reply address stay consistent across the rotation, so the customer sees no change in branding. The audit trail records when the rotation happened and who performed it.
Can we switch SMS gateways without rewriting workflows?
+
Yes. The SMS gateway endpoint sits inside the Channel Settings record. Switching providers means updating the endpoint and credentials in one place. Templates, workflow rules, plus triggered automation continue to work without modification, because they reference the channel rather than the provider directly.
How long does Channel Settings take to deploy?
+
Most deployments complete in weeks, not months. Channel Settings itself is two records of configuration, so the time is dominated by establishing the right SMTP and SMS gateway accounts on the customer side. PCG hosts the platform and answers the phone when something needs adjustment.
How does this connect to the Outgoing Message Logs and Template Managers?
+
Channel Settings sits underneath every send. The Email and SMS Template Managers hold the content. Channel Settings handles authentication plus routing. Outgoing Message Logs captures the result of every send. Together the four apps form a complete audit-ready outbound messaging stack that compliance can review without rebuilding history from raw logs.

Stop hunting for messaging credentials at 2am

One configuration record per channel. Secure credential storage, role-based edits, plus full audit history. Deployments measured in weeks, not months. Hosting by PCG with phone support included.

Request a Demo Contact Sales
Allison Woolbert, Principal of Phoenix Consultants Group
Allison Woolbert
Principal, Phoenix Consultants Group

Phoenix Consultants Group has built custom database and compliance software since 1995. Allison's personal software development experience predates that founding. Across 31 years, PCG has delivered 500+ applications spanning operational messaging, compliance tracking, plus audit trail systems for private-sector clients.

phxconsultants.com fireflightdata.com

Phoenix Consultants Group, founded 1995. FireFlight Data Systems is a proprietary platform hosted by PCG. Page last updated May 2026.

Clear Communication Starts with Clear Configuration.

Power every message from one trusted profile

Last updated: May 2026

Documents History: Every Certificate, Contract, plus Compliance File Tied to the Record That Needs It

Documents History is the FireFlight app for general operational document storage. Certifications, warranty records, purchase agreements, vendor contracts, plus internal compliance files are stored as encrypted records linked to any system entity. Expiry dates are tracked. Renewals get flagged. Nothing expires quietly.

Can FireFlight store every operational document tied to the right record, with expiry tracking on certifications? Yes. Documents History uploads files into encrypted database filestreams plus links each one to any system record: an asset, a part, a vendor, a user, a work order. Expiry dates trigger renewal alerts. Download activity is logged. Role-based permissions govern access. Deployment runs weeks, not months.

FireFlight Documents History screen showing operational documents linked to multiple system records with expiry tracking

See how a vendor certification expires next Tuesday, an alert lands on the compliance lead's dashboard, plus the renewal gets handled before procurement is blocked. Live demo or a direct call.

Request a Demo Contact Us

Why do certifications, contracts, plus warranties keep expiring without warning?

In 2026, most operations teams still manage their document expirations on a wall calendar or a spreadsheet somebody updates when they remember. A vendor certificate of insurance expires on the 15th. Nobody knows until procurement tries to issue a new PO on the 16th plus the system rejects it. A bonded contractor's surety lapses. A piece of equipment's warranty quietly times out three weeks before the gearbox fails.

The cost shows up as scrambling. Operations halts because a required certificate has lapsed. Compliance gets a finding because expired contracts were still on file as active. A warranty claim gets denied because the supporting documentation was archived in somebody's email instead of the asset record. None of these problems are mysteries when they happen. They are visible six months out, if anybody is looking.

Documents History fixes this by tracking the expiry date as a field on the document record itself. Every document carries a renewal date, a responsible owner, plus an alert window. When the renewal window opens, the assigned owner sees it on their dashboard. Compliance sees it on theirs. The renewal gets handled before the gap closes the door on day-to-day operations.

How does Documents History link one file to many records without duplicating it?

Every document is a first-class record stored in an encrypted filestream hosted by Phoenix Consultants Group. The file itself sits once. The links connecting that file to assets, vendors, work orders, users, or parts can be many. A vendor master service agreement uploads once plus links to every active work order tied to that vendor. A safety certification uploads once plus links to every user it covers. The MSA is never copied. The cert is never duplicated.

When the file gets replaced with a newer version, every linked record reflects the new revision the next time it loads. Prior revisions stay in the document history with timestamps plus user identity. The replacement event is logged so an audit can answer "which version of the safety policy was active on the day of the incident?" without anybody hunting through archives.

System-wide search makes the archive usable. Filter by document type, expiry window, vendor, asset class, or tag. Pull every active certification expiring in the next 60 days across the whole organization in one query. The same data point that prevents a compliance gap also produces the audit packet when a regulator arrives.

PDF Viewers Microsoft 365 Email Connectors

Your documents are your audit defense. We treat them that way.

Documents History files live in encrypted filestreams hosted by PCG. No third-party clouds, no staff laptops. Every upload, replacement, plus download is logged with user identity, timestamp, plus IP address.

Permissions govern access at the document level, not the folder level. A vendor's NDA stays restricted to legal plus procurement. An employee's certification stays visible only to HR plus the compliance lead, with every file open written to the access log. Prior versions are preserved so a regulator, attorney, or auditor can be answered from the file that was active when the work was done.

Ikhana, the FireFlight on-screen tutor character
On-Screen Tutor

Ikhana shows your team how to upload, tag, plus set expiry tracking in seconds.

Every field, every dropdown, every alert setting is explained the moment somebody asks. New hires upload their first document with full metadata the same week they start. No training queue. No tickets to IT.

Learn more about Ikhana

What does Documents History give your team?

  • Secure file uploads stored in encrypted database filestreams hosted by PCG. Files never sit on staff laptops or personal cloud folders.
  • Documents linkable to any system record. Assets, parts, vendors, users, work orders, plus any custom entity carry their own document history.
  • Upload plus replacement tracking. Every revision of a document is logged with user identity, timestamp, plus a preserved copy of the prior version.
  • Expiry date plus renewal tracking. Certifications, contracts, plus warranties carry alert windows so renewals get handled before the gap opens.
  • Download activity logs plus permission-based access. Every file open is recorded, plus permissions are governed at the document level.
  • Flexible tagging, categorization, plus advanced system-wide search. Pull every certification expiring in 60 days across the whole organization in one query.
  • Accessible from any relevant form plus through global document filters. The same archive is reachable from inside a record or from a system-wide search.
  • Multi-format support for PDF, DOCX, XLSX, JPG, plus other common business document types out of the box.
"With Documents History, we have eliminated the guesswork. Every file is where it belongs, always up to date."
Operations LeadEquipment Services Firm

31 years of operational software, with AI reporting built in for 2026.

Phoenix Consultants Group has built custom operational software since 1995. Documents History is one app inside the FireFlight platform, the same platform running fleet fueling for municipal operators, physician credentialing for staffing firms, plus airport ground equipment management for aviation services.

The AI layer added in 2026 means a compliance lead can query Documents History in plain English. "Show me every vendor certificate expiring in the next 30 days along with the work orders that depend on those vendors." The system answers from live data. No report request to IT. No waiting.

What changes operationally after Documents History goes live?

  • Certifications stop expiring quietly. The renewal window opens on the assigned owner's dashboard with enough lead time to handle it.
  • Compliance audits stop being a scramble. The archive produces a packet of every required document, filtered by date plus tagged by regulation.
  • Warranty claims get backed by the version of documentation that was active on the day of install or service, not a guess.
  • Vendor onboarding speeds up because COIs, NDAs, plus master service agreements upload once plus auto-link to every related work order.
  • Document scatter ends. The shared drive, the inbox, plus the desk-top folder stop being the system of record for files that matter.

Frequently Asked Questions

How is Documents History different from Manual Library?
+
Manual Library is purpose-built for equipment documentation: operator manuals, specs, warranties, plus setup guides tied to specific assets. Documents History is the broader archive for every other operational file: vendor certificates, NDAs, master service agreements, employee certifications, insurance docs, compliance reports. Both apps share the same encrypted filestream, but Documents History adds expiry tracking plus cross-record linking for files that touch many entities.
How does expiry tracking actually work day-to-day?
+
Every document with an expiry date carries a renewal window plus an assigned owner. When the window opens (typically 30, 60, or 90 days before expiry, configurable per document type), the owner sees the upcoming renewal on their dashboard. Compliance sees the same alert. If the renewal is not handled before expiry, the document gets flagged as lapsed, plus any dependent operations (procurement, scheduling, dispatch) can be set to require a fresh document before proceeding.
Can a single document be linked to assets, vendors, plus users at the same time?
+
Yes. A vendor's master service agreement can link to the vendor record, every active work order under that vendor, plus every employee authorized to act under it. One upload, many links. When the MSA is renewed, the new version becomes visible across every linked record in the same load.
What file types are supported?
+
PDF, DOCX, XLSX, plus JPG render in the embedded viewer. PNG, ZIP, CAD, plus other binary formats upload into the same secure filestream with a download option from the linked record. The supported viewer list expands as the FireFlight platform updates.
How are download events tracked for audit purposes?
+
Every file open plus every download is logged with user identity, timestamp, plus source IP. An auditor or attorney asking "who accessed this contract between these dates?" receives a precise answer from the system. Download logs are immutable: staff cannot edit or delete their own access events.
Can we bulk-migrate documents from email, shared drives, or a prior system?
+
Yes. PCG handles bulk migration during deployment. Existing files get mapped to the right records based on metadata, naming conventions, or a mapping spreadsheet your team provides. Expiry dates can be set during the migration so the renewal pipeline starts populating immediately on go-live.
How long does Documents History take to deploy?
+
Most deployments run weeks, not months. Phase one configures the document categories, permission roles, plus expiry alert windows. Phase two bulk-migrates existing files. Phase three is staff onboarding, with Ikhana walking the team through every screen the moment somebody asks. Operations leads typically see compliance benefit within the first month of go-live.
Allison Woolbert, principal of Phoenix Consultants Group
Allison Woolbert
Principal, Phoenix Consultants Group

Phoenix Consultants Group founded 1995. Allison's experience in software development predates that. 500+ applications built across small businesses, Fortune 500 firms, plus government contractors. Every call answered, with most issues on PCG-built software resolved the same day.

phxconsultants.com fireflightdata.com LinkedIn

Phoenix Consultants Group founded 1995. FireFlight Data Systems is the proprietary modular platform hosted by PCG. Page prepared May 2026.

No More Scattered Files or Lost Manuals

Keep vital documents connected to the records they support: with secure access, automatic linking, and system-wide visibility.

Last updated: June 2026

Demand Planning: Forecast What You Need Before the Shortage Hits

Demand Planning turns sales history, seasonality, plus live usage into forecasts your procurement and production teams can act on. See projected shortages early and plan orders around real demand, not guesswork.

Can FireFlight forecast demand from our own sales and usage history? Yes. Demand Planning builds forecasts from sales data, seasonal patterns, plus historical usage, then flags projected shortages before they bite. You pick the model, run what-if versions, plus track how accurate each forecast turns out. In June 2026 that means fewer stockouts and less cash tied up in overstock.
Demand Planning screen showing forecasts and projected shortages

See it on your own sales history. Not a canned demo.

Request a Demo Contact Us

Why do demand forecasts miss so often?

Most forecasts fail because they run on one input. A spreadsheet pulls last year's sales, someone eyeballs a trend, and the number that comes out ignores the seasonal spike everyone saw coming. When demand shifts, the plan does not move with it.

The cost lands in two places. Stockouts send customers to a competitor, and overstock parks cash on a shelf where it earns nothing. In 2026, with lead times still unpredictable and capital expensive, a forecast that is off by a week is a forecast that costs money.

Demand Planning pulls from more than one signal. Sales history, seasonal patterns, live usage, plus manual input from the people who know the account. The forecast updates as the inputs change, so the plan reflects what is happening now.

How does Demand Planning keep the forecast accurate?

Every forecast carries a model you choose. Moving average, exponential smoothing, plus a manual override when you know something the data does not. You version each forecast and run what-if scenarios side by side, so a planning decision is a comparison and not a guess.

The forecast ties straight into procurement and MRP, so a projected shortage turns into a purchase order before the gap opens. Accuracy tracking shows you which forecasts held and which drifted. Alerts fire the moment a number crosses a threshold you set.

Most deployments run in weeks, not months. Your sales and usage data comes over clean, and forecast views match how each planner works. The team stops arguing about whose number is right.

What apps does Demand Planning connect to?

Material Requirements PlanningMaterial Requirements Planning (MRP)
Inventory ControlInventory Control
Purchase OrdersPurchase Orders
Sales and POS data feeds Spreadsheet import and export ERP and MRP integration

How is your forecast data protected?

Your forecasts and the sales history behind them sit on a platform hosted by Phoenix Consultants Group, not parked with a third party you never picked. Access is set by role, so a planner sees the forecasts that belong to their accounts and nothing else.

Every forecast version and override is logged, so you can always see who changed a number and when the change happened.

What does Demand Planning give your team?

  • Multi-source demand input that blends sales, seasonal trends, plus historical usage into one forecast.
  • Flexible forecast models with manual override.
  • Forecast versioning and what-if analysis, so you compare plans side by side before you commit.
  • Live visibility into projected shortages.
  • Direct tie-in with procurement and MRP, so a forecast becomes an order without re-keying.
  • Automated update triggers based on thresholds you set.
  • Forecast accuracy tracking with alerts when a number drifts past your limit.
  • User-specific forecast views and filters.
With Demand Planning, we shortened our planning cycle from 10 days to 2, and cut inventory costs by 20%.
Director of LogisticsConsumer Goods Supplier

Built by people who answer the phone

Phoenix Consultants Group has built custom software since 1995. About a third of that work has been operations and compliance tracking for environmental and industrial firms. Demand Planning comes from that same hands-on line of work, not from a forecasting template bought off a shelf.

The same platform now adds AI reporting. A planner can ask a plain-English question about projected demand and get an answer back from live data, with no canned report and no waiting on IT. Most deployments still run in weeks, not months.

What changes operationally after deployment?

  • Planners build a forecast in an afternoon instead of a 10-day spreadsheet marathon.
  • Procurement orders against real demand.
  • Stockouts and overstock both shrink because the forecast updates as demand moves.
  • Every forecast carries a version, so a bad call is traceable.
  • Nobody argues about whose spreadsheet is right anymore.
Ikhana on-screen guide character
On-Screen Guide

Ikhana walks your team through every field

From the first click to the last entry, Ikhana sits on the page as your on-screen tutor. Every field, every button, explained the moment you need it. No thick manual, no support ticket.

Learn more

Frequently Asked Questions

Can FireFlight forecast demand from our own sales and usage history?
+
Yes. Demand Planning blends sales data, seasonal patterns, plus historical usage into a single forecast. You choose the model and adjust it by hand when you know something the numbers do not, so the forecast reflects the account, not just the math.
What forecast models does Demand Planning support?
+
Moving average and exponential smoothing are built in, with a manual override for the cases data cannot see. You can version each forecast and run what-if scenarios, so a planning choice is a comparison you can defend.
How does the app warn me about a shortage before it happens?
+
Demand Planning projects demand against current stock and flags the gap early. When a forecast crosses a threshold you set, an alert fires, so procurement can act while there is still time to order.
How long does it take to get Demand Planning running?
+
Most deployments run in weeks, not months. Your sales and usage history comes over clean, and the forecast ties into procurement and MRP. Planner-specific views are set up as part of the work.
Can different planners see their own forecasts?
+
Yes. Forecast views and filters are user-specific, so each planner works with the accounts and products they own. Everyone still pulls from the same underlying data, which keeps the numbers consistent across the team.
Does Demand Planning connect to our purchasing and MRP?
+
Yes. A projected shortage flows straight into procurement and MRP, so a forecast turns into a purchase order without anyone re-keying it. That closes the gap between planning a number and acting on it.
Allison Woolbert
Allison Woolbert
Principal, Phoenix Consultants Group

Allison has built custom software since before Phoenix Consultants Group opened its doors in 1995. Across 31 years she has delivered more than 500 applications, with about a third of that work in compliance and operations tracking for environmental and industrial firms. She answers the phone herself.

phxconsultants.com fireflightdata.com

Phoenix Consultants Group. Founded 1995. FireFlight Data Systems is PCG's hosted platform. Last updated June 2026.

Make Your Planning Process Smarter From the Ground Up

Align supply with demand before it’s too late with forecasting tools that help you anticipate, prepare, and perform at your best.

Last updated: June 2026

Dashboards: Your Whole Operation in One Live View

The Dashboards app pulls live data from across your system into interactive panels built by role. Track KPIs, statuses, plus real-time totals on one screen, so teams catch trends and act without digging through reports.

Can FireFlight show our whole operation on one live dashboard? Yes. The Dashboards app pulls live data from any app or module into panels built by role, with charts, gauges, plus alert indicators for thresholds and exceptions. You arrange it with a drag-and-drop editor and filter on the fly. In June 2026 that means decisions made on the spot, not after the export.
Dashboards app screen showing live KPIs and status panels

See it on your own live data. Not a canned demo.

Request a Demo Contact Us

Why does it take so long to know where things stand?

The status of a business lives in a dozen places. Inventory is in one app, open work orders in another, receivables in a third, and the only way to see the whole picture is to open each one and add it up in your head. By then, the picture has already changed.

That lag costs you. A manager makes a call on a number that was true yesterday, or an exception sits unnoticed because nobody happened to open the right screen. In 2026, when a problem can compound in hours, finding out at the end of the week is finding out too late.

Dashboards put the whole pulse in one view. KPIs, statuses, exceptions, plus real-time totals, arranged for the role looking at them. The number on the screen is the number right now, not a snapshot from a report someone ran this morning.

How do the Dashboards stay live and relevant?

Every panel feeds from live data in any app or module, so a dashboard reflects the system as it stands, not a nightly export. You build the layout with a drag-and-drop editor that sizes itself for the screen, and you choose the widgets that fit: charts, gauges, counts, grids, plus summaries.

From there, the dashboard works for the person in front of it. Role-based widget permissions decide who sees what, alert indicators flag a threshold or an exception the moment it trips, and filters narrow the view by date range, tag, category, or status. You can embed a view on a homepage or export the visuals for a meeting.

Most deployments run in weeks, not months. Your data already lives in the platform, so a dashboard has something to show on day one. The team stops switching between apps to piece the picture together.

What apps do the Dashboards pull from?

Inventory ControlInventory Control
Accounts and TransactionsAccounts & Transactions
Work OrdersWork Orders
Time Tracking on JobTime Tracking on Job
CertificationsCertifications
ProcurementProcurement
Invoices and QuotesInvoices & Quotes
Custom ReportingCustom Reporting
Ad-Hoc ReportingAd-Hoc Reporting
Software Subscription ManagementSoftware Subscription Management
Notes HistoryNotes History
Embedded homepage views Visual export for print and slides Role-based widget access

How is your dashboard data protected?

Dashboards run on the same platform that holds your data, hosted by Phoenix Consultants Group, not piped to a separate analytics tool you never vetted. Widget permissions are role-based, so a person only sees the panels and the numbers they are cleared to see.

An embedded dashboard respects those same limits, so a view shared on a homepage never exposes data beyond someone's permissions.

What do the Dashboards give your team?

  • Dashboards customizable by role, department, or function.
  • Live data feeds from any app or module.
  • Charts, gauges, counts, grids, plus summaries to fit the data.
  • A drag-and-drop layout editor with responsive sizing.
  • Alert indicators for thresholds, goals, plus exceptions.
  • Role-based widget permissions.
  • Embedded views on homepages or inside app contexts.
  • Filters for date ranges, tags, categories, plus statuses.
One glance at the dashboard and I know where everything stands. No chasing updates, no guesswork.
Director of OperationsMulti-Branch Service Provider

Built by people who answer the phone

Phoenix Consultants Group has built custom software since 1995. About a third of that work has been operations and compliance tracking for environmental and industrial firms, where a missed exception can become a missed deadline. The Dashboards app comes from that experience.

The same platform now adds AI reporting. Instead of hunting through panels, your team can ask a plain-English question about what changed today and get an answer from the same live data, with no canned report and no waiting on IT. Most deployments still run in weeks, not months.

What changes operationally after deployment?

  • One glance replaces opening five apps to check status.
  • An exception gets flagged the moment it trips.
  • Each role sees the numbers that matter to them.
  • Decisions get made on live data.
  • Nobody chases an update that is already on the screen.
Ikhana on-screen guide character
On-Screen Guide

Ikhana walks your team through every field

From the first click to the last entry, Ikhana sits on the page as your on-screen tutor. Every field, every button, explained the moment you need it. No thick manual, no support ticket.

Learn more

Frequently Asked Questions

Can FireFlight show our whole operation on one live dashboard?
+
Yes. The Dashboards app pulls live data from any app or module into panels built by role. KPIs, statuses, plus real-time totals sit on one screen, so the whole pulse of the operation is visible at a glance instead of across a dozen apps.
Is the data actually live?
+
Yes. Every panel feeds from live data, so the number on the dashboard reflects the system right now, not a nightly export. An exception shows up the moment it happens rather than the next morning.
Can I build a dashboard without a developer?
+
Yes. A drag-and-drop editor lets you arrange widgets and size them for the screen without code. You pick from charts, gauges, counts, grids, plus summaries and lay them out the way your team reads them.
Can different roles see different dashboards?
+
Yes. Dashboards are customizable by role, department, or function, and widget permissions are role-based. A person sees the panels and numbers they are cleared to see, so the same platform serves the floor and the boardroom.
Can a dashboard alert me to a problem?
+
Yes. Alert indicators flag a threshold, a goal, or an exception the moment it trips. You do not have to be staring at the screen for a problem to surface, because the dashboard marks it as it happens.
How long does it take to get the Dashboards app running?
+
Most deployments run in weeks, not months. Your data already sits in the platform, so a dashboard has something to show on day one. Training your team on the layout editor is part of the setup.
Allison Woolbert
Allison Woolbert
Principal, Phoenix Consultants Group

Allison has built custom software since before Phoenix Consultants Group opened its doors in 1995. Across 31 years she has delivered more than 500 applications, with about a third of that work in compliance and operations tracking for environmental and industrial firms. She answers the phone herself.

phxconsultants.com fireflightdata.com

Phoenix Consultants Group. Founded 1995. FireFlight Data Systems is PCG's hosted platform. Last updated June 2026.

From Data to Decisions, Instantly.

See the trends, spot the gaps, and take action with confidence all from a single, live source of truth.