BP to BP Questions / Clarification

[Ashley]

This has been done now, posted in Latest Updates:

It has become clear that some clients using the multi-channel feature require any invoices printed on the master site to reflect the order number and branding of the slave site. This is now possible via the new Company Options tab in the Channel Editor.

To make setting up as easy as possible, there is an option to populate all of the fields automatically from the slave site's company information. In order to make this possible, we have created a new "company" resource available via the API.

Great update, thanks.

[Simon - AS]

The delete operation is not intended to affect the slave, you'd have to delete it on both sites.

The best course of action for an order you wish to delete is to cancel it, leaving an audit trail if you need one.

So cancelling will affect the slave too?

[Rich]

So cancelling will affect the slave too?

Absolutely, anything you can do short of deleting the order affects the slave.

[Rich]

When the confirmation email is re-sent from the master site, the email seems to come from the master site domain, rather than the slave site. Is this a bug or is it by design? - I would have assumed the logical behaviour would be for this to trigger an email from the slave site.

This is now rectified, resending the order confirmation from the master site triggers the sending of the email on the slave site - in line with all of the other emails. To make this possible, I've created a new API "do_send_confirmation" parameter for the "orders" resource, meaning it's now possible to create an order via the API and also have the order confirmation email sent along with it.