hotwax / bopis Goto Github PK
View Code? Open in Web Editor NEWHotWax Commerce BOPIS App
Home Page: https://bopis.hotwax.io/
License: Apache License 2.0
HotWax Commerce BOPIS App
Home Page: https://bopis.hotwax.io/
License: Apache License 2.0
Not able to generate the packing slips for the BOPIS orders on the packed orders page.
User should be able to generate the packing slips from the BOPIS app.
The purpose of showing in-stock quantity is to help identify store inventory during picking+packing, QOH will be more meaningful information.
Consider the case that there is only 1 item in-store reserved for the order, it will show 0 in stock as the inventory is already reserved for that order and it will be confusing.
Also, we should not show it in the packed section as the item is already packed and the information is of no use.
When we click on 'ready for pickup' from the orders page, we get a message that order is packed and ready for pickup, but the order is not moving into the packed tab. The status of the order in OMS also remains reserved and does not change to packed though picklist is created.
Even when the picker function is disabled, the order is not moving into the packed order tab.
When clicked on ready for pickup, the order should move into the packed orders page and the status of the order in OMS should change to packed.
Packing slip field must have a card based UI similar to all the new revamped settings card
After activating Packing slip toggle, app screen must show option to generate packing slip for BOPIS orders.
For demo-oms instance- https://demo-oms.hotwax.io
In BOPIS app - https://bopis-v2.hotwax.io/tabs/orders
When the order is in the Open tab and clicks 'Ready for pickup',
The order is not moving to the Packed tab and shows an error something went wrong.
Shopify OrderId : #1706, #1703
After clicking 'Ready for Pickup' on the open tab, it should move to the Packed order tab.
While placing an order, some customers add handling instructions. In the current UI, fulfilment teams have no easy to access to read those handling instructions causing mishandling of orders.
Here is the Figma link:
https://www.figma.com/file/j3l0F2DioUHEuQT53NOQJY/Ionic-6-Material-UI-Kit-(Community)-(Nidhi--2023)?node-id=24777%3A91493&t=udkwTNLYSQZ2sujE-1
Currently, if an order item is rejected from BOPIS app the item goes to brokering queue, but store pickup order should not be brokered to any location for fulfillment.
Orders rejected in BOPIS app or store pickup orders should go to Store Pickup Rejected Queue.
Payload sample data for the API that rejects the order in HotWax when canceled in the BOPIS app
{ "payload": { "orderId": "11052", "rejectReason": "NO_VARIANCE_LOG", "facilityId": "WH", "naFacilityId": "PICKUP_REJECTED", "orderItemSeqId": "00103", "shipmentMethodTypeId": "STANDARD", "quantity": 1 } }
The current description is inadequate.
New description should explain how can users benefit from configuring pickers for the BOPIS orders
Note: This UI description is subject to change.
Shipping orders and packing slip configurations are showing up in the OMS section.
They should be moved to the App level section since they are settings specific this this app.
Use the new Shopify CDN compatible image component to fetch optimized images from Shopify instead of full size images.
You could take reference from existing PR. Use latest Luxon library
#107
Currently, On the BOPIS app's setting page, some of the field titles (like eCom Store, OMS) are appearing in English instead of Japanese after switching the language to Japanese.
eComStore and OMS should be in the Japanese language as well
Problem: The current handover process in the app allows users to assign pickers to orders. After the order is packed and completed, power users cannot easily track who picked the order and have to wait for reports. This scenario creates problems for power users when they need to resolve issues related to order item mismatches or missing items during handover to customers.
Proposed Solution: We must add a picker tracking feature to the handover process. This feature would allow power users to view the picker for packed and completed orders, making it easier to identify and contact the picker.
The picker tracking feature should be easily accessible for power user in the app's interface.
At the time of selecting a facility, no dropdown is visible even when the user is associated with multiple facilities.
The facility dropdown should appear with all the facilities the user is associated with.
Even though there are contact details on the ship group and order, they are not being reflected on the BOPIS app card or order detail page. This is most likely something to do with the way orders are indexed so assigning it to you first @adityasharma7, if its just a mapping issue you can assign it to @k2maan
If a user is associated with a facility in multiple roles, that facility is showing up multiple times in the facility switcher.
Even if a user is associated with a facility in multiple roles, the facility switcher drop down should only show unique facilities.
Associate a user with a facility as both a warehouse picker and manager. Login to the app and open facility drop down.
Improve the overall UI for settings page taking reference from Import app (hotwax/import#60)
If an user is not added to any facility, currently they can see orders for all facilities.
If a user is not added to any facilities, no orders should be visible to the user.
Ready for pickup button is only working till the text, after that if we click on the remaining area it lands on the order detail page
Area for action should not navigate user to the order detail page
Outbound shipments with the shipping method "Ship to Store" need a dedicated screen because they are not part of the normal fulfillment process. From the orders tab, there will be a button in the tool bar to navigate to a dedicated screen for these outbound shipments. Their status will be shipped, they will then be moved to scheduled for pickup, and then delivered.
Shipping orders field must have a card based UI similar to all the new revamped settings card
After activating Shipping orders toggle, facility/store should be able to view shipping orders along with BOPIS orders from the app screen
'Something went wrong' error is popping up while moving the order from Incoming to Ready for pickup tab in Ship to Store.
After that order is moved to the Ready for Pickup tab.
Adding Japanese translations will help users from Japan
Language switcher must be available for users who prefer different language to operate the app. This language switcher must have a card based UI similar to the new revamped settings card.
User must see the app in preferred language after switching the language from the settings page.
The BOPIS screen shows many product identifiers but many are redundant creating a cluttered experience.
The user should able to select their primary and secondary products identifier. Implemented using the DXP component for selecting product identifiers.
Authorization is one of the key features of the enterprise application. App should be able to identify the permissions associated with the current user and allow/disallow performing actions based upon it.
Once an order has been marked as ready for pickup, store reps cannot notify customers again to pick up their order.
There should be an option on the packed orders tab that lets store reps re-send ready for pickup emails to the customer on demand to help speed up the pickup process.
If a user navigates to a product page after searching a keyword on the list page, when they navigate back to the list page, their search result is cleared.
Navigating back from the product detail page shouldn't clear the search term and results on the product listing page.
Single order is generating two order cards in the Packed tab.
Single order should have only single order card in the Packed tab.
Email id not visible on the Order Detail page. Attaching the error logs:
TypeError: Object(...) is not a function
getCustomerContactDetails OrderDetail.vue:176
mounted OrderDetail.vue:186
un runtime-core.esm-bundler.js:2757
Yt runtime-core.esm-bundler.js:173
Xt runtime-core.esm-bundler.js:182
__weh runtime-core.esm-bundler.js:2731
fe runtime-core.esm-bundler.js:359
Y runtime-core.esm-bundler.js:6281
mount runtime-core.esm-bundler.js:4474
mount runtime-dom.esm-bundler.js:1607
cd49 main.ts:83
promise callback*cd49 main.ts:82
Long product names are hard to read. We should wrap the names so that the full name is always visible.
When creating a PR, the PR template shows to add a changelog entry, but we are not maintaining changelog entry
The note in the PR template should not be displayed
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.