DEVDOCS-6253 - Content Refresh - "Orders" (Storefront) #975
Conversation
Reformatted file with reusable schemas. Added new copy. Added missing fields and parameters. Called out legacy extra fields.
Co-authored-by: Terra Hyde <[email protected]>
There was a problem hiding this comment.
For these general endpoints: Verbiage like "by the Company user" is being used. But don't roles and permissions play into this? e.g., can't a particular company user have their permissions set such that ALL the company's orders are viewable by them? Or does that not affect the responses of these endpoints the way I'm thinking? (It's been a while since I was in the weeds on it.)
| description: |- | ||
| Generates an order record in B2B Edition after a Company user places an order. | ||
|
|
||
| This occurs automatically; however, you can populate extra information on a B2B order by using a [webhook](/docs/integrations/webhooks) that first listens for BigCommerce order creation and then calls the Create an Order endpoint. The request must be made within 10 seconds of an order's creation for it to be successful. |
There was a problem hiding this comment.
I'm a little confused on this. I just finished reviewing the server-to-server Orders API endpoints PR, and the same functionality exists there. Since this capability exists for the specific purpose of doing an asynchronous "override" of the native behavior, I'm unclear why there's a Storefront API version. If I have an app/integration and using a webhook to preemptively create a B2B order, what is the use case for doing that with a Storefront endpoint instead of Management?
Might just be worth clarifying with the B2B team.
There was a problem hiding this comment.
@bc-victor Do you know what the use case is for this Storefront endpoint?
bc-Vince
added
need-SME-review
Reformatted file with reusable schemas.
Added new copy.
Added missing fields and parameters.
Called out legacy extra fields.
DEVDOCS-6253
What changed?
Release notes draft
Anything else?
ping @bc-terra