Introduce recipes #1538
Draft
Introduce recipes #1538
+325
−2
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
krzysztofwolski
force-pushed
the
recipes
branch
from
7d95b9c to
04bd47a
Compare
krzysztofwolski
force-pushed
the
recipes
branch
from
04bd47a to
225d278
Compare
krzysztofwolski
force-pushed
the
recipes
branch
from
225d278 to
4f56075
Compare
krzysztofwolski
force-pushed
the
recipes
branch
from
4f56075 to
9754119
Compare
krzysztofwolski
force-pushed
the
recipes
branch
from
9754119 to
673949f
Compare
peelar
reviewed
Apr 18, 2025
| /> | ||
| </div> | ||
|
|
||
| # Setting up collection points |
There was a problem hiding this comment.
🚨 Markdown Police 🚨
suggestion: There should only be one # heading per document, so this one and the subsequent ones should be ##.
Comment on lines
+27
to
+33
| <div style={{display: 'flex', gap: '1rem', flexWrap: 'wrap', paddingBottom: '4rem'}}> | ||
| <CompactCard | ||
| name="Warehouses docs" | ||
| description="Read more about warehouses configuration." | ||
| link="/developer/stock/stock-allocation" | ||
| /> | ||
| </div> |
There was a problem hiding this comment.
thought: I know this is the closest we have to warehouse docs but it could be a bit misleading to be redirected to "Stock allocation" document when expecting to see warehouses. Maybe we should mark "Warehouse Docs" as worth revisiting and split into its own document to which we could link here in the future.
|
|
||
| Each physical location where customers can collect orders must be represented as a **Warehouse** in Saleor, even if you don't track inventory at that specific location. The Warehouse entity represents the physical address for pickup. | ||
|
|
||
| By choosing allocation strategy, you can choose if different warehouses will able to deliver to this location, or customers will be able to order only the products available on site. |
There was a problem hiding this comment.
suggestion: I think we should more explicitly say something like:
You should select "all warehouses" In the "Pickup" section of the Warehouse screen.
|
|
||
| # Storefront changes | ||
|
|
||
| List of available collection points for given checkout can be found in `availableCollectionPoints` field. |
There was a problem hiding this comment.
suggestion:
Suggested change
| List of available collection points for given checkout can be found in `availableCollectionPoints` field. | |
| List of available collection points for given checkout can be found in `checkout.availableCollectionPoints` field. |
Ideally, we could also add an example query.
|
|
||
| List of available collection points for given checkout can be found in `availableCollectionPoints` field. | ||
|
|
||
| To select it use `checkoutDeliveryMethodUpdate` mutation. Shipping address of the checkout will be updated to chosen collection point. |
There was a problem hiding this comment.
Suggested change
| To select it use `checkoutDeliveryMethodUpdate` mutation. Shipping address of the checkout will be updated to chosen collection point. | |
| To select it, use `checkoutDeliveryMethodUpdate` mutation. Shipping address of the checkout will be updated to chosen collection point. |
|
|
||
| When order is picked up, staff users can use Saleor Dashboard to update fulfillments status as delivered. | ||
|
|
||
| For integration with existing order management software create app which will automatically synchronize status with Saleor API. |
There was a problem hiding this comment.
style:
Suggested change
| For integration with existing order management software create app which will automatically synchronize status with Saleor API. | |
| To integrate with existing order management software, create an app which will automatically synchronize status with Saleor API. |
|
|
||
| Create products using new product type. Fill in the product details, such as name, description, category and add variants. | ||
|
|
||
| Create stocks for variants. Without them products wont be available for purchase. If your product has unlimited stock, turn off the "track inventory" setting. |
There was a problem hiding this comment.
style:
Suggested change
| Create stocks for variants. Without them products wont be available for purchase. If your product has unlimited stock, turn off the "track inventory" setting. | |
| Create stocks for variants. Without them, products won't be available for purchase. If your product has unlimited stock, turn off the "track inventory" setting. |
|
|
||
| When order is made and paid, make content accessible to the customer. Use webhooks to integrate with your business backend. | ||
|
|
||
| Create webhook in the dashboard. Choose `Order fully paid` event, define subscription query and target URL. When order is paid, Saleor will send data defined by subscription query to provided address. Now recipient application will be able to perform necessary operations like updating subscription details or sending an email with download link. |
There was a problem hiding this comment.
When order is paid, Saleor will send data defined by subscription query to provided address.
suggestion: link to https://docs.saleor.io/developer/extending/webhooks/subscription-webhook-payloads
| Saleor provides a flexible and powerful approach to multi-region commerce through its channels' management capabilities, allowing businesses to operate across various regions, currencies, and markets from a single backend instance. This recipe explores how to effectively set up and manage a multi-region shop using Saleor's channel architecture. | ||
|
|
||
|
|
||
| # Setup Channels |
There was a problem hiding this comment.
style:
Suggested change
| # Setup Channels | |
| # Set Up Channels |
or Channels Setup
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.
No description provided.