User Login and Info

The automatically created user gets an email about his account with login details. The user can then update their shipping and billing address or any other info from their My Account page.

Product Sync with Cron

When new product records came on Megabus, client wanted to update the products on WooCommerce to be similar on both ends. So we had to prepare a script to update products from Megabus and run that script occassionally to update the products on WC. The script had to utilize role based pricing to serve both retail and wholesale customers.

Frontend Feature

On frontend, client wanted to give users the ability to fill up the fields created earlier by admins. Users can fill up the field values are they want and then generate a printable PDF that he can print. We have used TCPDF for generating the PDF.

Multilingual Support

At the time of coding, we had to explicitly remember to put localization functions on the plugin to be able to make it support translation. We also had to implement separate urls for separate shops for separate languages. We had to iterate through the languages active on WPML to show fields for all the languages.

Customizable Options

We have implemented a customization option for T-shirt that every participant gets. It had options for extra T-shirts as well. One can order one or multiple number of T-shirts from the form. The T-shirt sizes were saved as variations and selections can be edited later from cart.

Cost Management

Our client wanted separate cost to be assigned for front and back design. We implemented a custom meta on the product edit page, which helps the client to set a price for the engraving for front and back separately. The cost is then used to determine the total of the order on the cart and placed with the order.

Rewards Program, Gift Certificates

Rewards program, gift certificate, vendor specific discounts, shipping discounts became very common things for our days with this project. We had some interesting issues to deal with. We dug up some solutions and at the end we were able to make all these work together harmoniously.

Our Solution

This is a fairly simple project with many sweet and complex details. We had to approach the project as a whole when planning. We had to make sure that our plan covers all the aspects – frontend, backend and email delivery – when the project is finished.

Here’s how we solved the problem:

Choosing the right API

We’ve had discussions with client. And our client decided that Mailchimp suited better for our needs than AWeber. It has a better interface, better documentation, better categorization etc. We also needed to add additional information with the entries to differentiate between persons – support for which was great on MailChimp.

Multilingual Emails

MailChimp helped us on the way. MailChimp has a good segmentation feature which we utilized for categorization. We simplified the process by preparing 7 separate lists for 7 languages. It made it simple for us to integrate and simple for client to manage.

User Management with Subscription Status

We had to use WC Subscription hooks to make sure that the user is listed only when he is subscribed to the service from the WordPress side of things. We had to test extensively for all the situations that might occur regarding the subscription status scenario. Client was helpful to setup a staging for us which helped us through the testing. We used normal subscription process with test payment method and Scheduled Actions combined to test the subscription.

Our Solution

This is a fun project but required careful planning. We had to be careful to implement features so that the aesthetics are not ruined. And we also had to take care of any existing functionality so that they are not disturbed.

Here’s how we solved the problem:

Controls on Admin

We prepared settings in such a way so that client can easily switch between new style and the old style. It helped keep the old product pages intact and the new changes remain on its own separate place, as client wanted.

Custom Templating

We had to implement a templating system for our unique requirements. We tried to keep it as separate from WC templates as much as possible. Ultimately this has let us make our changes as freely as possible, without disturbing the existing styles and templates. We had to implement a custom product slider and many other minor things, which we could then do easily. At the end, we were able to pack everything inside the child theme.

Designed with UX Builder in mind

The main content was made with UX Builder. So we had to work around it to implement various features. Documentation for UX Builder was scarce. And to make it even worse, proper hooks were absent as well. We had to find other routes to make it work.

Our Solution

This is a complex project. But we have prepared this to be as easy as possible. Plus, we have in depth articles and documentations to help anyone who wants to setup a microlearning platform.

Here’s how we solved the problem:

Customizable Default Product

We have prepared this to behave in Semi Automatic nature. There is a default product that can be set, which is at the heart of the plugin. The builder initially shows the default product, and as the user goes through the steps, it lets him change various attributes of it.

Product Attributes

Product Attributes are the part of nuts and bolts of the plugin. It works depending on the these attributes. The attributes are shown as steps and the user can change them to get the product he wants. Another thing is that we had to cancel any options that results in an empty list. So we had to design it in such a way that no option shows an empty list. Every choice leads at least one other option to choose from. It gets very intuitive and engaging once someone uses it.

Responsiveness

The builder has many elements. So it was a challenge to fit all these functionality into a small screen. It had different arrangements of elements for different screens. It was a good challenge for us and we have succeeded on it.