Feature Ideas

Trending
  1. Dark Mode for Ply Web and Mobile Application

    We’d like to request the option to enable Dark Mode in Ply, both in the web browser and the mobile application. What We're Requesting: A toggle or setting within Ply that allows users to switch between Light Mode and Dark Mode across all platforms - mirroring what many modern SaaS platforms offer today. Ideally, this could also respect system-wide preferences, automatically adapting to the user's device settings. Why This Would Be Beneficial: For users working long hours, especially in low-light environments or at night, dark mode greatly reduces eye fatigue. This is especially helpful when reviewing long catalogs, reports, or switching between job details throughout the day. Enhanced Accessibility Dark mode can provide improved contrast and readability for users with visual impairments or light sensitivity, making Ply more inclusive. Battery Efficiency on Mobile Devices Dark mode can reduce battery usage on OLED mobile screens - an important quality-of-life improvement for techs and admins who rely heavily on mobile usage in the field. Consistency Across Tools Many of our other software tools and systems offer dark mode, so switching between them and Ply feels disjointed without it. Adding dark mode would bring Ply in line with current UX standards and expectations. Suggested Implementation Ideas: Allow users to toggle dark mode in user preferences/settings. Optionally, support auto-detection of system theme settings (light/dark). Include support for both web and mobile versions of the app. We believe this feature would significantly enhance user experience for a wide range of Ply users, from field techs using the mobile app at night to admins working across multiple tools during long days.

    #28Andrey

    2

  2. Merge duplicate items

    #15Darion Miller

    3

  3. Cycle count reporting

    #8Darion Miller

    0

  4. Packout Management

    Enable techs to scan a Packout (barcode/NFC), adjust quantities for items used, and post those usages to jobs/transfers. At the end of each day, Ply tallies material consumption per packout (or per truck) and generates replenishment work: internal picks from warehouse and draft POs for shortages.

    #4Darion Miller

    1

  5. Purchase Reporting

    I would love to see a Report added to the Reports section that helps us better understand all of the things we are purchasing using POs.

    #48Adam

    3

  6. Vendor vs. Truck Stock Toggle by Job

    I’d like to suggest adding a toggle within individual jobs that allows users to clearly distinguish between materials coming from vendor receipts and materials being pulled from truck stock. Ideally, this toggle would: -Separate and label materials sourced from vendor receipts versus truck stock Show a total cost breakdown for: -Vendor-purchased materials -Truck stock materials -Allow users to quickly view or hide each category for cleaner job-level reporting This would greatly improve job cost tracking, accuracy, and visibility into how much of a job’s cost is coming from inventory already on hand versus new purchases.

    #104Ashley

    0

  7. ability to pick and choose which users receive the PO request

    rather than having all admins receive approvals for all PO's, give the ability to choose specific approvers - or assign approvals to a "finance" team member

    #264Joseph

    0

  8. Add "Stock Update Reason" Option to Desktop Quantity Adjustments

    Problem Description: Client has damaged, non-refundable stock and needs to deduct the quantity while also tracking the reason (damaged) for the adjustment. Currently, the option to select a stock update reason is only available when adjusting quantity via the mobile app (scanning or Edit Quantity), not on desktop. Current Behavior: On mobile, adjusting an item's quantity (via scan or Edit Quantity) prompts a "Stock update reason" list with options like Adjustment, Consumed, Damaged, Restocked, Returned, Sold, Stocktake, Stolen, Reconciled, Replenished, Deleted, Other Business, and Without Reason. On desktop, manually adjusting the quantity does not include this reason selection, so there's no way to document why the stock was reduced (e.g., damage) directly during the adjustment. Requested Behavior: Add the same "Stock update reason" selection to the desktop quantity adjustment flow, so users aren't limited to mobile when they need to document the reason for a stock change. Business Impact: Without this on desktop, users working from a computer (rather than the mobile app) have no way to track why stock was adjusted, for example, distinguishing damaged/unsellable inventory from other types of shrinkage. This limits reporting accuracy and makes it harder for office staff (who may not use the mobile app) to properly document inventory changes.

    #323Yvonne

    0

  9. Add Barcode Images to Inventory Export (Excel/CSV)

    Problem Description: Client wants to export the full catalog/inventory list to Excel so he can verify all barcodes work correctly with a barcode scanner gun. When exporting via Print & Export > Inventory mode, the barcode field only shows the numeric barcode value, not a scannable barcode image. Current Behavior: The Inventory export includes barcode numbers as plain text/numbers in the spreadsheet, but does not include the actual barcode image. Requested Behavior: Include the barcode as a scannable image (in addition to or instead of the numeric value) within the Inventory export file, similar to how barcode images appear in the Print & Export PDF/label formats. Business Impact: Without barcode images in the export, clients can't easily bulk-test or scan barcodes directly from an Excel file, they're limited to testing via the printed PDF/label format or the truck Inventory Log (which is only available for trucks, not warehouses). Adding this would give clients a faster way to validate barcode functionality across their full catalog regardless of location type.

    #322Firman

    0

  10. Require approval/authorization before a tech's stock transfer or material usage updates quantities

    Techs can move/use materials (via HCP job sync or direct transfer in Ply) and the stock quantities update immediately and automatically. The customer wants a way to "lock" truck stock numbers so they aren't affected until reviewed/approved, rather than having every material a tech uses at a job automatically become part of that truck's stock. Requested behavior: Add an approval step for stock transfers/movements — a tech-initiated transfer or usage would create a pending request rather than immediately updating quantities, requiring a Manager/Admin to approve it before the stock levels change.

    #321Joe

    0

  11. Auto-remove/deactivate catalog materials when stock reaches 0 (extend Special Order behavior to regular materials)

    Feature Request #1 Title: Auto-remove/deactivate catalog materials when stock reaches 0 (extend Special Order behavior to regular materials) Description: Customer: ACR Sedalia (Joe Crider, joecrider@acrsedalia.com) — HCP-integrated account. Problem: When a tech adds a material to a job in HouseCall Pro that isn't already part of their truck stock, Ply creates a new stock record for that material on the truck (via Location Response / Response Location deduction). Once the material is fully used, the stock record stays on the truck stock list at 0 quantity instead of being removed — forcing the customer to manually delete these entries. Because trucks are built from the same stock template but accumulate different "leftover" items over time via this mechanism, truck material counts diverge and the customer loses confidence in what should actually be on each van. Current workaround: Special Order items (created via PO with the "Set as special order item" toggle) already auto-deactivate/remove from inventory and catalog once consumed — but this only applies to materials created fresh through a PO as a special order line item. It cannot be applied retroactively to existing catalog materials, and doesn't cover materials that land on a truck via FSM sync. Requested behavior: Allow a "one-time use" flag (or similar) on regular catalog materials so that once a stock record hits 0 quantity — whether added manually or via FSM sync (HCP/ServiceTitan/Jobber) — it's automatically removed from that location's stock list instead of persisting indefinitely.

    #320Joe

    0

  12. inentory on trucks and from warehouse

    can we get the system to automatically deduct from truck to work order as used and when no more on truck to flag as no red because no more on truck the same goes for warehouse right now we transfer from warehouse to truck it adds to truck but not deducting as used on work order

    #319John

    0

  13. Ability to Bulk Upload Equipment

    Add the ability to bulk upload equipment, similar to the existing functionality available for materials. Currently, equipment must be added individually.

    #318Denaige

    0

  14. Buy in bulk, but items tracked individually and priced per piece not per bulk quanity

    It is useful because it will give a more accurate number on the worth of inventory in the warehouse.

    #317David

    0

  15. Ability to Differentiate "Assistant" from "Technician" Role in Multi-Tech Material Sourcing

    Currently, using the "Shared truck" sourcing strategy for multi-tech jobs requires every person assigned to the job, including assistants/helpers who are not the primary technician, to be set up as a full technician user with access to the shared truck location. This causes two problems: Assistants are treated as equal participants in the sourcing logic (tiebreaker rules, fallback behavior), even though they aren't the ones the sourcing decision should be based on. Because multiple people (tech + assistant(s)) are tied to the same shared truck, the Activity log records deductions as generic "general activity" against the location, with no way to attribute the action to the actual technician versus the assistant. Requested behavior: Introduce a distinct "Assistant" role (or a role flag), separate from "Technician," that can still be linked to a job/truck for visibility and access purposes, but is excluded from multi-tech sourcing logic entirely — it should not count as an additional assigned technician for "First technician's location," and should not be treated as a shared-truck participant for "Shared truck" sourcing or its tiebreaker/fallback rules. Why this matters: This would eliminate the root cause of non-attributable "general activity" entries under Shared truck, and would make sourcing logic more accurate for businesses that regularly staff jobs with a lead technician plus one or more assistants.

    #316Richard

    0