Continuing the discussion from Creating invoice in Producer accounting system for total products provided to Order Cycle:
What is the need / problem ?
The solution we created above is brittle (relying on a script running on the server) and unable to be shared with others. It is a partial solution, but with a few small refinements could enable a lot of things - like the highly sought after bank transaction upload files to streamline payments to producers
Currently it produces a row for each product if the variants are ‘summable’ and separate lines for the variants if not.
It requires an order cycle ID and a supplier ID - so at the moment it is just one supplier from the order cycle.
i have tested it this afternoon [NB. restricted access] and I’m pretty confident that both the taxes and fees are being picked up correctly. It might be missing the shipping fee - but it’s pretty close
So the modifications to deliver a total payment per producer would be
- run the script for all producers in an order cycle rather than just 1
- consolidate the rows per producer so there’s just one line each
- [check the shipping and payment method fees are getting picked up correctly]
AND put it on the API so everyone can just easily get and use it
Who does it impact ?
People wanting to generate bank files
What is the current impact of the problem ?
Mostly the influx of farmers markets using OFN who are concerned about manually making payments
What is the benefit of focusing on this ?
There are many use cases of these potential API endpoints. Moving in this direction can give instance managers a lot more power to provide elegant and customised solutions for users
Potential solutions that will solve the problem ?
- Continue the frustrated hack approach
- Tweak the script
- Make it available to everyone to install on their servers
- Maintain it
- Put it on the API so we can all easily use it
Selection of a feature candidate
Est. time is that same or less to put on API, and robustness and useability of the solution much higher for everyone
T-shirt size of our selected feature candidate
Small. One day to create a new API endpoint based on the current script.
Metrics to measure if need is satisfied after feature is implemented
Epic/projet where you can follow implementation
Connected wishlist and discovery discussions*
[list precedent discussions]