• Resolved James Revillini

    (@jrevillini)


    I might be going about this the wrong way, but here’s the workflow I had in mind – let me know your thoughts.

    BACKGROUND
    I’m using this and a combo of plugins for an invoicing system. I know I can create orders in the Woo admin but it’s clunky and time-consuming. By using this alongside Product Tables I hope to make this work…

    1. login as admin
    2. go to shop (product table – achieved with plugin)
    3. switch to {client user} (i have a plugin for this)
    4. add items to cart + checkout with invoice option.
    5. user gets email with link to view order (invoice)
    6. button to pay is available <- this is what is missing

    COMPARISON
    If I manually create an order in woo, by default it:
    – puts the order status as pending
    – emails them that the order/invoice is ready to be paid
    – when they view their orders, it offers a PAY button (I’m guessing it’s bc a payment option ISN’T set)

    POSSIBLE SOLUTIONS
    SOLUTION #1
    I thought about trying to hook your gateway and unset the payment method when it’s placed on the front-end and the payment method is invoice, but here’s my thoughts/questions:
    1. will that cause certain triggers NOT to fire in your plugin?
    2. it’s not really accurate … the order method IS pay via invoice, and then it BECOMES pay via card or whatever once that happens. I like data to be accurate so this solution feels like a hack.

    SOLUTION #2
    Hook something in the templates for the customer order table and order view page which shows the PAY button when the current method is invoice and it’s on-hold or pending payment.

    #2 seems like the better approach. Do you agree? Am I missing some faster/better way?

    There is one other thing that bugs me about Woo in general… if I generate an order on the backend, by default it sets the status to ‘pending’ and fires an email to the customer. But if I have your plugin set the status to pending with a front-end checkout, no email is generated to the client. Is this your experience as well or do you think I have a conflict with another plugin.

    THANKS FOR READING ALL THIS!

  • The topic ‘Give user option to pay via another payment method later’ is closed to new replies.