1.create order tag
Create action for void
create action to get reason
4.create rule to apply when item get voids
5.create rule to store reason for void
Report:
[Voids Detail:1,1,3,1,2,1, 1]
>User|Time|Item|Quantity|rea|status|Total
{REPORT ORDER DETAILS:O.User,O.Time,O.MenuItemName,O.Quantity,OSV.GStatus,OS.GStatus,O.TotalPrice:(OS.GStatus=Void)}
Welcome back @madiha. Thank you very much for the tutorial.
For anyone interested this tutorial shows a different method for configuring gift and void reasons.
If we have pre loaded values in Void (Automation Command), then can we show the Tag like this below the item
VOID:AUTOCOMMAND VALUE SELECTED: REASON
For Ex:
Void: Order Changed by Customer: Wants to try something else
Right Now it works only like this Void: Wants to try something else
Can you help ?
Not in a single state.
Void is a gstatus state name and you then have state value which could be one or the other.
You could in theory expand and have ‘changed by customer wants something’ as a combined singe state value.
Alternatives could be using the void state value for one part and a seccond separate state like void reason for the seccond part or an order tag maybe for the seccond part of the options.
Or Instead of showing Void
Just show this
Order change by Customer: Wants to try something else.
FIXED COMMAND VALUE: REASON
If you wanted however depending on report setup you may end up with micro reporting of ‘void’ command reason.