I agree with Josh(and also Tim, of course) as programmers/managers/etc. we should try to overthink about what the user is trying to obtain. Users are quite miopic when expressing their needs and even that particular mental process to attain that info. I have some users that ask pretty specifc things and I end drilling them with questions to see if the process is a one time thing or if it looks it will be something that will spread for more cases.
That being said, the fact is that sometimes I have prepared “nice” configurable solutions for problems that end changing their parameters and render the solution useless. That is a risk also and we could argue that then I didn’t do a good job at obtaining the actual requirement and developing the solution, but I am pretty sure that we all have been there.
Sometimes(depending) it is better to deliver a first entry development so the users end up defining the final and “real” permanent solution.
Sometimes, done is better than perfect. As so eloquently put in Agile terms.
Sounds like you need to farm some of this work out to that REST pro contact.
I used to be horrible about documentation, hard coding etc… it always haunted me down the road. If anything, i have learned so much over the last two years since i started Agile Scrum project management, not only from iterative development, but gathering requirements that can be somewhat nebulous from USERS (four letter word), architecture a bit upfront pays dividends for everyone, users, other developers (future self) and lends credence to IQ/OQ/PQ which is all about delivering something that works and is scaleable as business needs always evolve and sooner or later someone will be revisiting that work down the road. All good thoughts here…
THIS
Reminds the to ask Epicor to remove the 36 Check Limit Hardcoded and 10000 rows per Multi-Company Run Hardcoded. 
When you load in 3million parts, you can wait a few days for all the MC stuff to propogate properly from Master Company.
When you hardcode Volume:
Hey… hardcoding of things like, “MFGSYS” Site id, and other features when you create a company are my favorite complaints… you can’t have that as a Rant either… it is my rant… hahahhaah
(Glad everyone is feeling better now that they have ranted a bit).
Oh, that’s right. This was Tim’s rant about hardcoding values…
Yeah, it doesn’t take much time to code a User-Code entry lookup for many hard-coded situations. 
