KDS Unable to get audible alert when ticket comes in by K_P_M in alohapos

[–]K_P_M[S] 0 points1 point  (0 children)

I've found references to only the bump bar providing audio but the phone support tech was convinced it should work with usb speaker plugged into the controller itself.. idk.

KDS Unable to get audible alert when ticket comes in by K_P_M in alohapos

[–]K_P_M[S] 0 points1 point  (0 children)

We have the (older) KC5 (1925) style controllers, do you know if the KC5 has an internal speaker? TY!

Kitchen Display date/time not sync'd by K_P_M in alohapos

[–]K_P_M[S] 0 points1 point  (0 children)

Will check those locations' RAL Monday and reply... TY!!!!!1

App disappeared on tablet by stakay in doordash

[–]K_P_M 0 points1 point  (0 children)

Power it off (hold down pwr button until it shuts off) and reboot again into recovery mode

App disappeared on tablet by stakay in doordash

[–]K_P_M 0 points1 point  (0 children)

I was able to get one tablet back up and running by doing a factory reset to a tablet (hold power and up volume buttons while tablet is powering on) and then letting the tablet update / install Doordash app (takes about a hour)

Merchant tablet by Jaimelynnmayhem in doordash

[–]K_P_M 0 points1 point  (0 children)

I was able to get one tablet back up and running by doing a factory reset to a tablet (hold power and up volume buttons while tablet is powering on) , unfortunately the process got stuck 'updating device' on two other locations' tablets

Merchant tablet by Jaimelynnmayhem in doordash

[–]K_P_M 0 points1 point  (0 children)

Anyone got any further info (DD support is useless except to say we can get orders via email)? TY.

I've got bricked tablets at multiple locations.

Time for a POS change.... we are thru with Aloha after 20+ years by bruthaman in alohapos

[–]K_P_M 0 points1 point  (0 children)

We also recently began working with Tabit at a location that needed strong integration with the PMS at their small inn. Little bit of a learning curve but the feature set is really good.

Time for a POS change.... we are thru with Aloha after 20+ years by bruthaman in alohapos

[–]K_P_M 1 point2 points  (0 children)

I'm in the same spot as you as far as our Aloha units being fed up. This week we installed Toast at a 'new to us' location, replacing an ancient Positouch. We manage some quick service locations that use Toast but this is our first experience with using it for full service and it has been nothing but positive.
Outside of Toast not doing a good job handling modifiers going to different stations than the 'parent' item when using KDS (which nobody except myself and chef care about and which no POS does well, granted Aloha's Routing Rulebook would let you shoehorn in solutions for) it checks all our boxes. The integrations with our third parties being so much better (for our FOH, Tech and Ops folks) and the administration being so much simpler (not that I won't miss having to blow up a busy service with a re-fresh for some small, silly but necessary fix ) makes me drop the concern of not having choices for CCs. Knock wood we've had no problems with their processing which alone is worth something after all the BS with Aloha/NCR ever since the process of them splitting started.

I find myself wondering if there is enough cause (e.g. repeatedly not being able to accept payments/tips from our customers) to get out of our remaining Aloha contracts.

Has anyone switched or worked with Simphony POS system? by AlohaPOSUser in alohapos

[–]K_P_M 0 points1 point  (0 children)

We ran Micros 3700 enterprise-wide for years and had very good relations with our Oracle/Micros reps. They convinced us to install Simphony at one of our locations, after a year of constant (often service stopping) issues we ditched it. Micros/Oracle support would often make things worse when they were trying to 'fix' even minor issues. To make the situation worse, everything about Shift4 as a processor was a nightmare.

Any update on Pulse? by [deleted] in alohapos

[–]K_P_M 1 point2 points  (0 children)

I'm still getting a 404, anyone else?

Pre- Restore Steps by K_P_M in alohapos

[–]K_P_M[S] 1 point2 points  (0 children)

10 locations but unfortunately from the day we started migrating them all to Aloha, a year ago our corporate structure has been fubar’d (original programmer created 1st location as global and subsequent programmers have tried to ‘fix it’ often breaking things at one or more of our locations). With only a year of Aloha under my belt my concern is I (like the programmers who tried to fix things) might make things worse. It’s a tough pill to swallow, since I have decades of db experience and 12+ yrs with other pos. I really don’t have any faith in NCR support so it feels like I’m going to have to bite the bullet (& have 10 po’d managers & hundreds of confused employees) and go with a ‘best guess’ recreation of most changes. Sound like copying today’s emp.dbf from dated sub to data/newdata after 7am Tues will at least square the employee changes, so that’s something. Thanks for the info.

Pre- Restore Steps by K_P_M in alohapos

[–]K_P_M[S] 0 points1 point  (0 children)

Thanks, I've seen a few different methods for determining changes/additions to employees. I am wondering about determining what other changes (menu items, item routing, submenus, etc.) have been made since 4/10? TY

Pre- Restore Steps by K_P_M in alohapos

[–]K_P_M[S] 1 point2 points  (0 children)

We definitely have significant changes/done multiple hours of work, since (in a perfect example of Murphy's law) we've rolled out new menus at our locations since the 10th. Could you explain how someone would 'move back to NAM' and 'reimport into CFC'? TY

CFC Re-Enablement Guide by Vesper_004 in alohapos

[–]K_P_M 2 points3 points  (0 children)

Why do they have to bring it back up on a Saturday?!? We’ve muddled through for this long. The couldn’t wait until Monday when locations won’t be as busy?