Citrus-Lime Backoffice

Hello, can we please have a function to print/email credit notes?

Currently there is no way of tracking how postage charges effect margin. Some bikes (or orders) always have a carriage charge against them. It would be useful to have a box where the postage cost could be entered and then averaged over the items on the order.

Would it be possible to have the Gift Voucher redemption code printed as a bar code on 40col receipts? It would speed up the redeeming of vouchers and look more professional.

In Backoffice 2.0 please could the receive stock scanning be embedded on the page so that when you scan an item it makes a live change to the received stock counts on the page. In current backoffice you scan in to a box that does it in the background but if you have scanned many items this is open to errors by the time you hit complete on it. Much better to have visibility as you are scanning. This worked very well in the days of Microsoft RMS.

Would be great to have the ability to freeze the first column or two as I scroll to the left and right through the wizards. I find myself having to expand the window size across 2 monitors to be able to see what I'm doing. Obviously I can get rid of columns to make it more manageable if I'm able to.

I thought it was worth posting this video of the backoffice 2.0 picklist which has just gone across to testing. The speed is awesome which we are seeing throughout the new product. https://www.loom.com/share/e2577ee5995949c78451ce395fc6e1a3

Basically a more advanced CRM tool based on customer purchase history. The service reminders are nice but with certain services (like broken spoke, new derailleur) added to the a service item the original intended service interval can be stretched further than first desired. Examples of purchase related intervals we've used prior to Citrus: new bike -> 7 day thank you / reminder of 30 of free adjustments / 1 year bike birthday tubeless tire work -> 4 month notice to stop by and get sealant refreshed tune ups -> it's nearly been a year since your last full service (similar to current) winter sale tune ups -> you took advantage last year do so again no sales for XX days -> we haven't heard from you in a while coupon WorkstandIQ (formerly Retail Toolkit) does this currently.

It would be better if Order Status reasons were customisable like other reason codes so that we can adapt these to work to our own internal processing and way of working. I am referring to the status on customer order drop downs. We use drop downs to signal orders at certain statuses however the configured term used is not accurate. We "just know" that we mean something else..

When doing similar assemblies being able to copy a previous one as a starting point and making small edits would save time.

When you're scrolling down a big Purchase Order, the header row disappears so you can't see the column titles anymore.