Mike Hurt (Director, Dymin Systems)
My feedback
10 results found
-
3 votesMike Hurt (Director, Dymin Systems)
supported this idea
·
An error occurred while saving the comment -
30 votesMike Hurt (Director, Dymin Systems)
supported this idea
·
-
18 votesMike Hurt (Director, Dymin Systems)
supported this idea
·
-
35 votes
An error occurred while saving the comment Mike Hurt (Director, Dymin Systems)
commented
***EDIT: I see now this was already suggested, but it works great for us, integrates well with Quickbooks as you can set custom GL account mappings per product ID, and gives us excellent reporting (QB-side reporting, the RS reporting is still terrible).
Here's how we do it, and how we've done it in our prior POS/Inventory software: Use Discount Codes!
Create a category called Discounts. Directions here: https://feedback.repairshopr.com/knowledgebase/articles/511237-discount-on-an-invoice
But how it works out is you create a bunch of products in this category that each are your discount types you want to track. We start all the codes with DISC- so employees can quickly pull up a list of them when adding to a ticket/sale. A few examples of what we have:
*DISC-FB1 Facebook Promotion (Half off Repair)
*DISC-REFERRAL Referral Card Discount $40 off any service
*DISC-CLIENTNAME We have a few of these we give discounts to employees of businesses with Service Agreements.
*DISC-EMPLOYEE Employee discounts
*DISC-ABANDONED Code for writing off abandoned equipment
*WTY-L-STD Code for standard warranty claims
*WTY-L-GOLD Code for a "gold" warranty claimsJust add the product code to a ticket at a negative sale price. You can either have the code with a set dollar/percent amount or leave it $0 and staff will be able to enter a variable discount.
The way you get reporting is unfortunately not so great, but that's just because of RepairShopr's poor reporting comparable to our other software. But at a basic level the "Sales by Product" report pulled on the Discounts category gets you a selectable-time-period sum total if discount quantities and dollar amounts. You can also do a Sales Detail report and export to CSV to get invidivual instances of sales. We just wish there was a tab within each product called "Sales History" and listed each instance of sale of that product in a filterable fashion. Currently you can only pull sales data by Category or by exporting to CSV and doing your own work.
-
1 vote
An error occurred while saving the comment Mike Hurt (Director, Dymin Systems)
commented
Hey, I was in your same boat of logic in thinking this was a problem, so I did some testing and wanted to share in case others have the same issue.
-Certificate Numbers do not need to be unique! They can run over on each other with no negative impact. The numbers serve no purpose in the system other than what gets printed on the PDF.
-You can start all warranty templates at Cert# 1 if you want, and then you have an easy count of the total number of that warranty you've sold.
-The max certificate # you can start with is 100,000, but it still works beyond that and continues to increment 100,001+So in my opinion, just start all your warranty numbers at something like 1000 and just let them all increment as they end up doing.
-
23 votes
An error occurred while saving the comment Mike Hurt (Director, Dymin Systems)
commented
I'll add to this that only showing the Product ID is pretty silly. Are we supposed to memorize what all the random number SKUs are? Please add a visible column selector to include Description and Vendor SKU.
To add to the original request for a Vendor column, this would be incredibly useful. You support multiple vendors and multiple vendor SKUs per product, which s great. We just need to be able to specify a default vendor per product, which is what Pending Orders would look to to group products by Vendor on Pending Orders screen.
My old product (before RepairShopr) was miles better than RS on procurement and maintaining stock levels. I can send screenshots and have intimate knowledge on how this should work, and I'm happy to work directly with RepairShopr devs on developing this. We're very hamstrung at this point in time with RepairShopr.
Mike Hurt (Director, Dymin Systems)
supported this idea
·
-
14 votes
An error occurred while saving the comment Mike Hurt (Director, Dymin Systems)
commented
This was formerly raised in 2018 and declined https://feedback.repairshopr.com/forums/165658-general/suggestions/17832151-edit-ticket-comments
But I'm going to also agree that it should be possible. Any other ticketing software I've ever used allows admins to edit notes.
Deleting and re-adding is not a solution, because you also cannot change the time-stamp, leading to the logical flow of ticket being completely off.
Simple solution: Allow (with relevant Permission option in settings) editing any note field. Note now shows "edited" near the upper right. Admins can view prior iterations of the note.
If you still want to restrict Emailed notes, that's fine. The system shouldn't allow emailing of Private notes. That's the whole point of Private vs Public. If it's emailed, the notes is Public and you could lock that from editing. Any other note type should allow editing.
With respect to Gazo's concern, that would not be an issue since it could be controlled by User Permissions. Draft versions of notes would not be necessary, just make them editable. I wouldn't even care of it didn't keep an audit-trail history on the notes, if you want to lock Public notes. There's no reason to prevent editing Private notes.
Mike Hurt (Director, Dymin Systems)
supported this idea
·
-
8 votesMike Hurt (Director, Dymin Systems)
supported this idea
·
An error occurred while saving the comment Mike Hurt (Director, Dymin Systems)
commented
I agree, and will add that Bundles don't allow serialization of the product until Invoicing. Seems crazy. How are you supposed to do computer builds? Parts used need to be serialized when they're pulled and before assembly happens. What are you supposed to do, take the computer back apart at check-out time to get the serial numbers?
Can you tell me how you're working around this?
-
6 votes
An error occurred while saving the comment Mike Hurt (Director, Dymin Systems)
commented
Upvote for Ryan @ Pinella's solution. I agree, all configurable lists of data entry types should have a hidden backend ID# that keeps them all unique, so you can edit the Description of any field's data points without losing associations for prior items that reference that selection. This is common sense programming.
As a minor workaround, if you're just looking for historical data on a customer with Referred By value that may have been deleted because you no longer use that source, you can do a Customer Export from Admin>Reports that will still retain old text. You could use this method to update Referred By in Excel in bulk, then just make sure all current entries match options in RepairShopr settings and import the changes.
I also want to throw out that having the default 5 required options is silly. Why require anything at all? The way you have them conflicts with the way I've been tracking customer sources for 20 years. I can't create "Referral" because that logically conflicts with "Customer" and "Friend" that are required. But what if it was a business they were referred by? Just silly. Let us make our own lists.
-
24 votesMike Hurt (Director, Dymin Systems)
supported this idea
·
I agree. A sequential numerical number is the correct way to number Purchase Orders. What repairshopr does with the date and some abbreviation of the vendor is atrocious.
For example, our vendor which is named "AVW, Inc. dba Max Pro" creates PO #'s that look like
"A,I.DMP-20210331-1"