Upload, Source, Map, Deliver
One clear path from vendor file to approved ERP loadsheet.
Upload a messy pricelist. Review a clean source.
Rubi PL applies the cleanup and standardization needed across sheets, rows, columns, and values, then shows the result before mapping.
The cleanup happens before mapping, while the source remains available for review.
Map source columns to ERP fields
Map one or more source columns to each ERP field, set fixed values, clean and combine text, and apply common pricing calculations such as markups, discounts, margins, percentages, and averages. Preview the result and save the mapping for reuse.
Review changes and prepare the delivery
Review proposed rows, warnings, and available comparison results. Separate matched and new products, review price and cost changes, preserve selected fields, and download the files when they are ready.
Current destination
Q360 is the first supported destination.
Rubi PL brings in current Q360 product data, compares it with the proposed loadsheet, and gives your team a clear review before downloading the import files.
Bring in current product data
Refresh Q360 product data before preparing the next loadsheet.
Review what changed
See matched, new, changed, and missing products in one review.
Keep selected fields
Preserve descriptions, item types, and other values your team already manages in Q360.
Reusable mappings
Update pricelists without starting over.
Reuse approved mappings
Save a mapping, use it again for later files, and archive it when it is no longer needed.
Keep every revision
Replacement files preserve the original delivery and show mapping changes that need review.
More than 100 AV vendor mappings
We plan to deploy more than 100 validated mappings for leading AV vendors, giving teams a faster starting point for each new pricelist.
Future roadmap
Where Rubi PL is headed next.
Planned directions for expanding inputs, destinations, reusable data, and connected actions.
More ERP destinations
Planned destinations include NetSuite, QuickBooks, Odoo, D-Tools, and Improoved. Downloadable import files may arrive before direct connections.
Direct updates to connected systems
We plan to support reviewed updates and cleanup in connected systems.
PDF pricelist support
PDF pricelist support is planned.
Master Catalog
We plan to let customers find and add approved products from a shared catalog without a pricelist.
Buy-and-sell marketplace
We plan to let customers list selected overstock inventory for purchase by other Rubi PL customers.
Need hands-on help?
Pricelist management is also available as a separately scoped Rubi Works service.
Rubi can help prepare and review pricelist work when the engagement calls for operator assistance beyond the software workflow.
Frequently asked questions
Questions about Rubi PL.
What file types does Rubi PL accept?
Rubi PL accepts XLSX, XLS, and CSV vendor files.
How does Rubi PL clean up messy vendor pricelists?
Rubi PL finds the useful product data across sheets, cleans and standardizes it, and shows the result before mapping.
What can my team review before downloading the files?
Rubi PL shows the proposed rows, warnings, and available comparison results so your team can review changes before downloading the import files.
What happens with an unfamiliar vendor file?
Supported spreadsheet files can use the guided mapping workbench. Operators map source columns to destination fields, preview the result, and save the mapping for reuse. Files with more complex layouts can be reviewed with Rubi.
What happens when a vendor sends an updated pricelist?
Upload the new file as a revision, reuse the saved mapping, review what changed, and approve the new loadsheets.
How can my team get started?
Talk with Rubi Works and bring one representative vendor file. We will review your import workflow and determine whether Rubi PL fits your use case.
Bring one real vendor file.
We will walk through the file, your import process, and whether Rubi PL fits the way your team maintains product and pricing data.
Guided onboarding starts with one representative vendor file.