Correct Redo coverage line item values in custom returns integration docs - #190
Merged
Steven Mitchell (smitch5777) merged 9 commits intoAug 14, 2026
Conversation
William Schaefermeyer (WillsWebsites)
approved these changes
Aug 14, 2026
William Schaefermeyer (WillsWebsites)
left a comment
Contributor
There was a problem hiding this comment.
Can we remove all the stuff from this guide that is trying to explain about the requests and schemas and auth and just reference the API endpoint for it. this guide can get a lot more lean and just be truly a guide if we do that
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
_redo_typeexample value:return->returns_redo_typetakes precedence overtags, and thatpriceSeton the Redo line item drives billing__final_sale_coveragefor final sale returns coverage