Leaderboard

I wish all of the blesta users and their families a Happy Easter ..

Happy Easter to you too mate.

Decided to have one of our support guys play around with it and he manged to fix it. Have no idea what he did but at least it works now!

Hi, First of all, i am not sure i can post this here, if not please tell me, i will delete it right away. I didn't see a thread that can ask for review. We are about to lauch a market place next month. Just posting link to it's dev site to know review from community so that i can consider that before releasing final version. Link to dev site is http://alltoolkits.com/devPlace/ PM me if you need test login details to check more inner pages. Thanks

Happy Easter.

Happy Easter.

The screenshots don't do it justice. These new order forms are incredible, and we've designed them to be super flexible. We didn't just slap together a few order form templates and toss them in. There's a lot of engineering and user expeirence design put into this release. The end result is pure awesome, and the best order forms in the industry by far.

Happy Easter!

+1 Thanks for you to

Note that CORE-923 mentions caching the invoice on disk, which sounds .pdf only. The data as it appears on the invoice should be stored in the database as well, as you also need it to be able to generate reports from it, in order to fill in your tax return properly. One needs the customer's country and customer's VAT ID as it was on the day the invoice was issued at a minimum. (Need to supply the government with a list containing the VAT IDs of companies in other EU countries VAT was exempted/reverse charged for, and the total amount sold to that company in a reporting period) But better to stick all other invoice data in the invoice table as well, just in case any other jurisdiction needs more. Also not sure how caching on disk as described in CORE-923 is going to work when generating a single pdf containing multiple invoices (print queue thing?), and viewing single invoices earlier or later. Do you plan to store the invoices as single pdfs on disk, and use a library (such as Zend_Pdf or FPDI) to concatenate them when generating a batch? Or does it still end up generating fresh invoices containing possibly new data, which is a problem?

I made a note regarding invoices being changed in the task when I created it, and it's something we will consider. However, I think proforma invoices once implemented (In CORE-497) will solve any concerns about invoice amounts & payments changing after they are created. If proforma is enabled, a proforma invoice will be issued. Paying the proforma invoice will generate and pay a typical invoice. Combined with CORE-923, you can be pretty sure invoices will not change at all once they are created.

Information on invoices Invoices should never change once issued. Remarks about payments only belong on invoices if the payment was made PRIOR to the invoice being issued. If you asked and received payment in advance, the invoice you send must (under EU rules) mention the date the payment was made. Usually this is done by having a line at the bottom like "Already paid by <payment method> on <date>", where you would normally have payment instructions instead ("Payment due in 14 days. If paying by bank transfer please mention reference ABCD") One issue with Blesta is that when a new order is placed by the customer and paid directly by credit card, the invoice is created first and the payment applied after that. Think it would be better if that was reversed. Do not issue an invoice until gateway confirms payment (or issue a pro-forma invoice first, if the customer wants to make a manual payment) That way you do can mention the payment that was made on placing the order. And not creating invoices until the first payment arrives also reduces unnecessary tax liability, for orders placed but for which the payment process was never completed. Credits Credits should be rare and not an everyday occurrence. If the customer accidentally paid too much when paying a previous bill, you really should refund it to whatever payment source it came from, instead of hanging on to it as credit. If you offer the customer a discount (e.g. when he is upgrading from a smaller package he already paid for, to a bigger package), mention the discount as a second invoice line with negative amount. This also reduces the tax to pay properly, something which will not happen if you just give him some credit for it. (Partial) payments after invoice has been issued If customers have problems paying their bills in full, make partial payments, and have problems keeping track of how much is left to pay, the proper way would be to send them a separate account statement listing transactions and outstanding balance. Not append later information to an invoice issued previously.

Hi Paul, Just wanted to throw a quick line in here letting you guys know that I'm perfectly okay with a Beta being released today (Saturday). I know it's the weekend and you guys might have some concern about releasing so I just wanted to go ahead and let you know that I'm okay with it.

Yep, you can link directly to a specific item on the order form. Mike's right, it will just make the item pre-selected on the order form though, at least for the ajax one. I have to check, but for the wizard type, you may be able to link to the 2nd page where you configure a specific item. If so, this would bypass the package selector and go straight to configuration which may be preferable. The new "default" order template in 3.2 will be Wizard Boxes, I think it's likely to be the most used order form.

Not yet. A mass mailer plugin is planned as part of CORE-621. There's a good chance it will be included with version 3.3.