Forums

Covering OroCommerce, OroCRM, OroPlatform topics, including community updates and company announcements.

Forums OroCommerce How to enable client pickup

This topic contains 8 replies, has 4 voices, and was last updated by  Mauro Chojrin 10 hours, 44 minutes ago.

  • Creator
    Topic
  • #37734

    Mauro Chojrin
    Participant

    Hi:

    I’m new to oroCommerce (I’m familiar with Symfony).

    I’m testing the platform on behalf of a client who offers two options for goods delivery:

    1 – His own trucks do the delivery
    2 – The clients can pick their orders up at the warehouse.

    Form what I could see so far, those options aren’t available out of the box, so I’m building my own custom shipping methods… Is there an integration I can use instead?

    Thanks

Viewing 8 replies - 1 through 8 (of 8 total)
  • Author
    Replies
  • #37735
    Michael
    Michael
    Keymaster

    Hi Mauro,

    Is there any logic associated with these shipping method?
    Would it be sufficient to simply use different labels for Fixed Rate shipping method?

    #37741

    Mauro Chojrin
    Participant

    Hi Michael:

    Thanks for your answer :)

    I think the fixed rate method will do partially… Once it’s in place I’ll need to keep track of which vehicle (and driver) did the actual delivery.

    For the other method (client pickup) I need to incorporate a little scheduling mechanism (Basically, the buyer should let the provider know a timeframe within which they’ll be stepping by the warehouse).

    #37743

    Mauro Chojrin
    Participant

    Ok, a little update on this:

    I created a new shipping method (NullShipping) following this guide.

    What I haven’t figured out yet is how to remove the example options (I basically replaced “FastShipping” references with my own) and show the buyer a form to enter pick up details…

    Also, I believe I’ll have to integrate with a fleet management system… anybody knows of one? Ideally it’d be a Symfony Bundle… I’ll post it here if I find any good one.

    #37784

    Mauro Chojrin
    Participant

    Another question I have here is how should I manage the versioning of my code.

    At first I created a new repository with two remotes (One for the official oroCommerce code and a second containing my particular installation which also had my own code).

    I would then point production to my own remote in order to get the my code together with any updates from oroCommerce but this seems a littel too complicated…

    Should I create a particular repository for my src directory or what do you suggest?

    #37834
    Andrey Yatsenko
    Andrey Yatsenko
    Moderator

    Hi Mauro,

    “src” directory is located at an application and it’s easier to manage it at the single repository.
    OroCommerce doesn’t make any code changes at the src directory, so it’s should be easy to pull changes from the second origin on patch releases.
    You should pull changes from the last released tag at the application repository of OroCommerce. It will contain updated composer.lock file that leads to the latest compatible OroCommerce and third-party dependencies.

    To manage your own code versioning you could use any strategy, there is no any limitations from an application side. We are using semver.org, but this will be overkill for the private project. I suggest, the easiest way will be to version production ready releases by the release date.
    Every new version represented by the new tag in your application git repository that contains all the custom code in the “src” directory.

    #37869

    Mauro Chojrin
    Participant

    “src” directory is located at an application and it’s easier to manage it at the single repository.
    OroCommerce doesn’t make any code changes at the src directory, so it’s should be easy to pull changes from the second origin on patch releases.
    You should pull changes from the last released tag at the application repository of OroCommerce. It will contain updated composer.lock file that leads to the latest compatible OroCommerce and third-party dependencies.

    I’m not sure I understood this suggestion…

    Should I create my own private repository just to store the src directory or should I put everything in there? (I’m not so versed in git either, so any resource would help here :).

    My understanding is I’d have a private repo, then I’d be pulling from OroCommerce and pushing to my own and in production I’d pull from the private… is this what you’re suggesting?

    To manage your own code versioning you could use any strategy, there is no any limitations from an application side. We are using semver.org, but this will be overkill for the private project. I suggest, the easiest way will be to version production ready releases by the release date.
    Every new version represented by the new tag in your application git repository that contains all the custom code in the “src” directory.

    Ok, that sounds right. Since I’m the only developer so far I thought about using a simple scheme: master + develop branches (and perhaps I’ll take your idea for tagging).

    Thanks!

    #37879
    Yevhen Shyshkin
    Yevhen Shyshkin
    Participant

    Hello, Mauro.

    As for repository – you may just fork or clone required application repository (e.g. https://github.com/oroinc/orocommerce-application), do all the development in your private repository and use it in production. Then you can merge changes from public repository from time to time to get the latest fixes and packages.

    #37882

    Mauro Chojrin
    Participant

    Yes… I guess that’s what I’ll be doing.

    Thanks!

Viewing 8 replies - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.

You will be redirected to [title]. Would you like to continue?

Yes No
sso for www.magecore.comsso for oroinc.comsso for oroinc.desso for oroinc.fr