November 3rd 2022 update
Changes (status) in bold 
We ticked two things from the roadmap 
Yet it will be tough to finish this in 2022 as we are facing performance issues on production servers. However moving things forward is still doable 
-
Split checkout: No changes. Currently in beta-test. Only one critical bug left
More info here https://community.openfoodnetwork.org/t/new-checkout-feature-split-checkout-rollout/2546/20?u=rachel -
Tax reports: No changes. First stage on our big reports project. Tax reports will be enhanced. Welcome deeper granularity, hasta la vista rounding errors! [Reports] Tax Totals Report · Issue #6847 · openfoodfoundation/openfoodnetwork · GitHub
-
Backoffice UI uplift: Main PR has been updated and hopefully can reach final code review soon. First step towards Network 2.0 - our product list is getting a face lift. Also AngularJS will be removed from the product list. This will lay the ground for every shiny new experience network 2.0 is about.
Also on the tech side, it will enable us to really start our Styleguide framework (think of it as a catalogue of pre-designed elements our developers can cherry pick!)
Context: Backoffice Product List table user interface uplift 1
-
Cut down testing suite length by 5 min on github Actions : This is moving forward, see last testing catchup. We use Github tools to run the automated tests we have (the suite). this takes 20min to run. Lowering this time should ease contributions and day to day work on the project
-
OIDC authentication: DONE. This is funded by the Data Food Consortium project. First step into more interoperability is to ensure we can authenticate users and share only their data - when they agree to it. OIDC is a web standard that allows users to login on apps. As this is a first prototype, instances will be able to choose whether or not they want to activate OIDC. Also note that we will only handle login for accounts which already exists. You can do account creation with OIDC, but this is out of scope of this funding. There are rooms for improvement (like login/logout on the same browser no matter the website, but we will see this in other DFC tasks in the future).
-
DFC product API: In progress. Next steps (funded by DFC project + AU and UK) are around getting our product catalogue on the API and handling create/update/delete actions! This means we need OFN API product endpoints to be updated in v1 first!
-
Linking order cycles to shipping and payment methods: DONE
. This work has been started by Cillian as a contribution from OFN Ireland! Funded by CA, US, UK and FR, we will be able to tag shipping and payment methods to OC! An issue remains on multi-distributors order cycles. This is currently handled by a potential new core dev.
Up next (no changes)
What will happen next?
We still have some compliance work to do. In particular: History of invoices changes and numbering system: in the EU, invoices should carry the history of order changes and have a numbering system fitting requirements. On the bright side, we won’t have any more support requests starting with “I swear I haven’t deleted anything on the order…those eggs really disappeared!!”
Our reports project needs to go forward : especially improving packing reports, and reports used to pay producers (among many other things the product team needs to tidy-up and order! )
Network phase 2 needs to kick-off.
Aside of this a number of needs seemed to reach a consensus after the user interviews (this is not a priority order):
Speaking as a hub manager
- I need to send alerts to my customers
- I need to have an alert when max orders is reached in an OC
- I need to manager stock info from producers
- I need to adjust orders
- I need to process refunds in bulk
- I need to propose discounts and vouchers
- I need to let my customer pay with credits
- I need to have donation options at checkout