We did make a start on a Vendr Portal package, but it's currently still in progress and isn't scheduled in to be finished any time soon.
You can see where we got to with the source code on our git repository at https://github.com/vendrhub/vendr-portal This basically currently has the bits to registers, reset passwords and login.
The extra bit you would need is a dashboard with order history which we don't currently have, but we do have API methods on the order service to GetFinalizedOrdersForCustomer where you can pass a customer reference and it will return a list of orders for you to render.
Hi Matt,
Its 2022 I know now but we are getting across Vendr and really liking it so far. I came across this from googling.
There is a fair bit of work on said portal BUT the thing we were looking at is Umbraco Members.
I could not see anything to link to Umbraco Members. If you had that in place then developers would then naturally be able to do a lot in this area and more themselves.
If you could have a customer correspond to a member or even ultimately on initially setup say if your using Vendr Customer or have member associated with the order instead.
Vendr would - Create a New Member Type - Customer and that being used.
From that, because its an Umbraco Member we can easily create login areas and then based on the member pull the associated orders so you would not have to offer a seperate solution.
With that as well with what we are doing people can link (which there are already various solutions) to 3rd party CRM's, link with payment gateways to have saved payment solution tokens by extending the Member (which you would do on the customer type) and then have syncs etc and so on and so on.
Would work there be a bit more viable and leave developers to do their own thing knowing Umbraco?
Seconding this. Is there an existing way to tie Vendr to Umbraco Members? We'd like to require people to sign up for an account to be able to complete the checkout process.
Vendr isn't really tied to anything, however we have assumed that generally these are most likely to be Umbraco members.
The only thing Vendr does is store a memberReference against an order. What that is we don't really care, but OOTB just before you place an order, we will get the current logged in member in Umbraco and use their member key as the memberReference
With regards to sign up / log in, this is all basically Umbraco patterns so you can set those up however you see fit. Likewise, you can built it into your solution that before you checkout you must log in (several people have done this).
The Vendr Portal package is aiming to be just the customer area from where they can view past orders. So far there is some login logic there, but it's not fully in place. We would then just use the members key to lookup orders for that member and display them on the order history page.
Regarding requiring login / registration, I think that's out of the scope of the Vendr Portal package. But maybe this should form part of the Vendr Checkout package I'm not sure.
As long as you have a means to tie the member to a customer it is good. Customer does seem a bit too closely packaged with an order though, it would be nice if it was a bit more of its own object scope.
We found shipping methods great but also not easily able to expand and while we mapped out a scope for 3rd party integration it's not as straight forward as we would like.
Often and a lot these days a store owner wont ship the items and its a fulfilment centre or a specific shipping company that will handle the leg work there so a site would often connect to a 3rd party based on shipping address to calculate and then display.
We can see how to do it, but I think you will see what I mean with it's not as smooth as it could be.
But again loving a lot about Vendr. Mainly because the API is thought out, events are there (So often missed) you would hope to be there. Properties available as you would expect (and far too often in solutions are not)
Yea, we do appreciate our shipping configuration atm is quite simplistic and it is our plan to extend and improve this to allow more customisations. Unfortunately we don't have a timeline on this just yet as there are few things that really need to be put in place to get us there so it's going to be a step by step approach.
Many thanks for the feedback. It always good to know where Vendr could do with improvements 🙏
Thanks Matt,
Expansion of options for shipping - when it comes it comes :)
But if a virtual shipping option of kind that could be supported so 3rd shopping options can have get the value and name to populate that order as the selected one without having one or more in backend you got to do messy stuff with would be great. At the moment order is all looking for existing shipping options.
You could use 1 shipping option and store the other info as order properties for the time being. If you need to affect price you can use a IShippingCalculator to do this. Would either of these work?
Customer portal to view all their orders
Hi,
Is there a way for a customer to login to the site and view all their orders for updates etc?
This is one of my potential customers requirements.
Nick
Hi Nick,
We did make a start on a Vendr Portal package, but it's currently still in progress and isn't scheduled in to be finished any time soon.
You can see where we got to with the source code on our git repository at https://github.com/vendrhub/vendr-portal This basically currently has the bits to registers, reset passwords and login.
The extra bit you would need is a dashboard with order history which we don't currently have, but we do have API methods on the order service to
GetFinalizedOrdersForCustomerwhere you can pass a customer reference and it will return a list of orders for you to render.Hope this helps
Matt
Hi Matt, Its 2022 I know now but we are getting across Vendr and really liking it so far. I came across this from googling. There is a fair bit of work on said portal BUT the thing we were looking at is Umbraco Members. I could not see anything to link to Umbraco Members. If you had that in place then developers would then naturally be able to do a lot in this area and more themselves.
If you could have a customer correspond to a member or even ultimately on initially setup say if your using Vendr Customer or have member associated with the order instead.
Vendr would - Create a New Member Type - Customer and that being used.
From that, because its an Umbraco Member we can easily create login areas and then based on the member pull the associated orders so you would not have to offer a seperate solution.
With that as well with what we are doing people can link (which there are already various solutions) to 3rd party CRM's, link with payment gateways to have saved payment solution tokens by extending the Member (which you would do on the customer type) and then have syncs etc and so on and so on.
Would work there be a bit more viable and leave developers to do their own thing knowing Umbraco?
Seconding this. Is there an existing way to tie Vendr to Umbraco Members? We'd like to require people to sign up for an account to be able to complete the checkout process.
Vendr isn't really tied to anything, however we have assumed that generally these are most likely to be Umbraco members.
The only thing Vendr does is store a
memberReferenceagainst an order. What that is we don't really care, but OOTB just before you place an order, we will get the current logged in member in Umbraco and use their member key as thememberReferenceWith regards to sign up / log in, this is all basically Umbraco patterns so you can set those up however you see fit. Likewise, you can built it into your solution that before you checkout you must log in (several people have done this).
The Vendr Portal package is aiming to be just the customer area from where they can view past orders. So far there is some login logic there, but it's not fully in place. We would then just use the members key to lookup orders for that member and display them on the order history page.
Regarding requiring login / registration, I think that's out of the scope of the Vendr Portal package. But maybe this should form part of the Vendr Checkout package I'm not sure.
As long as you have a means to tie the member to a customer it is good. Customer does seem a bit too closely packaged with an order though, it would be nice if it was a bit more of its own object scope.
We found shipping methods great but also not easily able to expand and while we mapped out a scope for 3rd party integration it's not as straight forward as we would like. Often and a lot these days a store owner wont ship the items and its a fulfilment centre or a specific shipping company that will handle the leg work there so a site would often connect to a 3rd party based on shipping address to calculate and then display. We can see how to do it, but I think you will see what I mean with it's not as smooth as it could be. But again loving a lot about Vendr. Mainly because the API is thought out, events are there (So often missed) you would hope to be there. Properties available as you would expect (and far too often in solutions are not)
Hi Liam,
Yea, we do appreciate our shipping configuration atm is quite simplistic and it is our plan to extend and improve this to allow more customisations. Unfortunately we don't have a timeline on this just yet as there are few things that really need to be put in place to get us there so it's going to be a step by step approach.
Many thanks for the feedback. It always good to know where Vendr could do with improvements 🙏
Matt
Thanks Matt, Expansion of options for shipping - when it comes it comes :) But if a virtual shipping option of kind that could be supported so 3rd shopping options can have get the value and name to populate that order as the selected one without having one or more in backend you got to do messy stuff with would be great. At the moment order is all looking for existing shipping options.
Hey Liam,
You could use 1 shipping option and store the other info as order properties for the time being. If you need to affect price you can use a
IShippingCalculatorto do this. Would either of these work?This is along the lines we were looking to do :)
is working on a reply...