Order statuses configurable

[ogrosko]

It would be nice to have a possibility to define Order statuses (add, remove, modify).
Right now they are hardcoded ...

[duncanmcclean]

Out of curiosity, which order statuses would you like to add?

[ogrosko]

@duncanmcclean we need statuses like:

• Shipped partially
• Complete
• Complain

etc ...

[Polecalex]

I agree with this. I'm working on functionality that would benefit from statuses like:

• Redeemable
• Redeemed

It would also be useful to link these with custom events, triggering email reminders or extra functionality.

[sandervankasteel]

I agree to the previously made comments. I am currently trying to "shoehorn" support in for a status called "Send to manufacturer". Getting this support for this OOTB would be fantastic.

[sandervankasteel]

@duncanmcclean quick question.. if I were to create a PR for this functionality, would you consider merging it?

[duncanmcclean]

At the moment, probably not.

We're looking to improve how revisions & publishing workflows work in Core, and as part of that may make entry statuses configurable.

I'd prefer to wait until that's done before implementing configurable order statuses in Cargo so I can mirror its approach, rather than needing to invent something custom.

I hope that makes sense. I know it's not ideal for you right now, but its definitely something that's on the back of my mind. 🙂

[sandervankasteel]

That makes perfect sense. Because at the end of the day, the maintainer(s) of the project are responsible for it and it should fit into how they want the code to look and work like.

It is not ideal for me, but I'll do so workarounds, no worries 😉

[Polecalex]

If it's worth anything to anyone, I've managed to create a temporary solution that works fairly well for me - it may also work for others.

Instead of making any changes to the status system, I've manually added a new field to the Blueprint class under sidebar called "Stage". "Stage" simply pulls a custom stage variable from the order and displays it nicely in the sidebar, above date.

As this will be reset when updating Cargo, I've also got a simple post-update-cmd script that amends the field automatically. Adding it to the blueprint file is mainly for looks but you can also just add it as a normal field using the correct blueprint route for orders under resources/blueprints/vendor/cargo/order.yaml

Again, this solution may not work for everyone but it allows me to keep track of what I'm doing alongside the actual order status.
You'll just need to figure out what Status partially aligns with your custom stage.