hivesolutions / budy Goto Github PK

Description

It would be useful for several scenarios to be able to specify taxes in each bundle line (while having the bundle taxes be the sum of all of them) instead of having just a taxes field for the whole bundle.

Why

So that you can discriminate between an item's base price and its taxes component, which is useful in several use cases, such as calculating commissions based on the liquid value of an item.

Description

A method for listing existing referrals, similarly to what happens with vouchers.

Description

When using the operation "Export complex" in Orders, the CSV only contains a total field with the final price.
It would be desirable to be able to export the all price components (base price, taxes, DDPs, discount and shipping).

Why

A new and automated workflow that automatically fills all the current fields in the form should be created to allow a more fluid and efficient workflow.

What

Add support for auto-filling the "Import Seeplus" form with the metadata from the order.

How

Approach 1

Use configuration variables to obtain the configuration mapping of our store information to the one present in Seeplus and then use it to fill the form. This configuration should be a string with the serialized contents of a JSON object.

Approach 2

Use the meta configuration in the Store entity to store information about the Seeplus ID associated with each store. In addition, we can also "mark" the default store for fulfillment.

Resources

• Example order - https://budy.lugardajoia.com/admin/models/orders/6563b15e382862059fc2111b

Description

Be able to easily distinguish, via a model attribute, if an order has the same address as the store it is associated with. In practice, this means knowing if set_store_shipping or similar methods were called in that order.

Note: I also think it would be useful if this new attribute/flag could be in list_names.

Why

It is useful for easily making decisions that depend on the order being shipped (or billed) to the store or not.

Current solution

Compare order.shipping_address with order.store.address attributes one by one.

Description

There should be proper wishlist support under the Budy infra-structure, with features like:

• Add to wishlist
• Empty wishlist
• Migrate (total or partial) to bag
• Recalculate prices based on dynamic or fixed approaches

Description

Operation export complex in orders gives error 500 500 - 'short_description' not found.