May or may not be something the staff here find interesting , but one project I have been following for the last year is MessagePack C#.
Check it out, watch it, formulate your own opinion.
Mentioning it only as a possible means of improving serialization (every byte counts) 🤭
Q&A modules/add-ons are a dime a dozen but the ones that super excel at it are far from common. If built into the platform, bonus.
Here's the skinny:
Product page showcases questions and answers
For every question on a product page a new web page is dynamically created.
Allow customers to submit photos, text, etc.
Dynaically generates a webpage that hae all the submitted photos and text. Along with an authoritative reply and public replies (if permittef by store owner).
Why do it this way? It generates a ton of new surface area for search engines to use, attributing all the quality relevant questions to the store domain, and each independent page can be setup to use FAQ schema.
Additional bonus points if the system allows customization of Net X days, thus preventing those customer accounts from purchasing on credit (terms) if their previous purchases have not manually or automagically been designated as Paid by the store owner within the term timeline.
I.e. overdue accounts can't purchase more.
While some of my earlier suggestions might not be a major requirement for some. I want to propose Purchase Orders as a big one for most B2B vendors.
Allow store owners the ability to allow certain customers to be able to pay by purchase order.
At checkout customers with the appropriate permissions should be able to enter a PO number and bonus points if the system allows them to upload an optional pdf/doc of their PO.
These customers in most B2B settings are Net 15, Net 30, Net 45 customers. Meaning they have credit of a predetermined amount that allows them to purchase. Payment must be made within the net terms, which is a slightly movable boundary in most real world scenarios.
Nice work on the release G team.
I must say one of the things that keeps me involved in checking out the latest commits and progress is your dedication and momentum on the project. You folks don't sit still, I think thats a big factor in whether a project sinks or swims. Long term perseverance. The project keeps getting better and better.
Product level discounts are good. Category level tier discounts might be another good avenue to explore.
Infrastructure in place for schema plugin development
Having experimented for the last year with other larger platforms like shopify (yoast seo) and bigcommerce (manual dev), one of the emerging plugins that i saw a bit of interest in as of late is properly marked up schema.org json+ld or microdata.
The tricky part is in variants, if you do not want to create an individual product for each variant (colour swatch, product pick list, radio buttons) then having the infrastructure in place to handle plugin development that can manage proper schema for all products is a great start.
If i have some time (rare as of late) this upcoming weekend, i can post a guide on ubuntu 18.04 bionic beaver, install and setup, if that helps?
In the meantime, have you tried to compile (build) in a local directory and publish to the nginx/html/ directory with appropriate permissions ?
I suppose one way would be to upload their specific RFQ format, to their custom account. Associate the fields with a part number you want to search for.
Or to make it more extensible, allow any customer to upload their own rfq format and then you have to build a way of letting them map those entities to your product #'s.
Thus, when they upload it would search based on the previously mapped entities.
I realize it is "custom oriented" service that puts this stress on the seller however i wonder if it is just easier to say to them, go ahead and log into your account and search for the items on our site. Have a nice day.
So ive come across RFQ lists from certain customers where they basically try to do exactly what you said. Let's say on average we get 1-4 items per line but i could see it being larger in other cases.
Typically sent to us in excel format.
I guess my question is, how do you associate a line on their rfq list with a specific inventory item of:
1. They misspell it
2. They dont use a part # of yours but instead use a manufacturer part number
3. Each RFQ is formatted differently ? (I.e. column 2 contains MPN while another rfq comes MPN in column 3 with the description.
How can you standardize a way of implementing this thst ensures it is extendible into the future and works with more than one customer rfq format.