Application DevelopmentUI/UXOn-Demand Developers


Our client oversees a global food distribution business that operates out of Chile . Soon, the client will add another location within the US in support of their international campaigns. They are in the middle of building a warehouse in Orlando to house these efforts.

Their main deterrent of international growth is their monolingual IT support. Prior to contacting Chetu, the client used an application engineered in FoxPro that was programmed purely in Spanish. In support of their future outreach, the client recruited Chetu to build an application that supports both Spanish and English.

To nurture our relationship with this client and eliminate all language barriers we assigned one of our Spanish-speaking project managers to the client's application development project. Not only were we focused on meeting the language requirements, but also redefining the workflow to maximize ease of use.

From kickoff, we met the business hours of the client, expediting time to market and working as an extension of their internal structure. Although we were nearly 4,500 miles apart, we were able to work alongside our Chilean client to introduce a bilingual technology into a rapidly growing market.

bilingual app
Desktop to mobile experience


Within the application, we decided to optimize some of the preexisting UI, while also introducing additional modules. These modules needed to reflect both US and Chilean culture. We would build a customer portal so that the client would be able to see their details and create requests for reception and dispatches.

We will be installing the existing client app developed in FoxPro technology and analyzing all existing functionality to deduce where the pain points are. We would then create a new database, finalizing the UI for all modules and implementing a robust set of functionalities.

In development, we will first work on the Calendar task and reception module. After completing this module, we will move onto the other modules. This includes verifying with the client by giving an interim release and after getting the final go-ahead, we will create the customer portal and complete the warehouse portal.

To move forward with the project, we digested the client's legacy code—taking time to understand the database structure and documentation.


During development we leveraged the following technologies:

  • Framework: .NET Framework 4.6.1
  • Application Type: MVC5 Web Application
  • Language: C#
  • IDE: Visual Studio 2017
  • Database: SQL Server 2016
  • Change Management Control: TFS
  • Device Compatibility: Desktop, Laptop, Tablets, Mobiles
  • API: N/A
  • Tools:
    • Bootstrap (For responsive UI)
    • ELMAH (For error logging)
    • Ninject (For dependency injection)
    • Jquery
    • PixelAdmin theme
    • Entity Framework 6.0 (For database access)
    • Itext Sharp (For Reporting)

Development environment also includes Visual Studio 2017. The application is a web-based application developing in MVC5, while the old app was built in Visual FoxPro in the client's environment. We tested the new application within the client's database, and deployed once we tested.

TFS Repository holds all the code a central repository. The developer can download the latest code from the repository in their local machines. Database script is also present on TFS. In terms of the staging environment, we used Microsoft Azure.

Although we referred to the existing app, we did not use any of the source code. We, instead, engineered a totally new SQL database to support the new application. Users have easy access to feature whatever data they need to work on. The app features full-width viewing without excessive pop-ups, which was an issue with the legacy app.

The app is able to run on different browsers and different devices like desktops, laptops, mobiles, and tablets. This cross-channel access gives flexibility to users, working from different environments. Data can be stored locally in the Warehouse database or stored in centralized hosting that keeps all data on the same server.

There app is programmed with the following high level modules—

1. Calendar: Create Task, Requested Task, Reports, and Task Type.

2. Reception: Enter Reception, Reception Acts, Reports (Finalized Receptions and Reception Summary), Configurations (Truck Load Style, Receptions Documents, Insurance Companies)

3. Storage: Assign Location, Change Of Position, Reprint F.U.A, Storage Reports, Location Reports)

4. Dispatches: Dispatches Entered, Dispatch Acts, Reports (Finalized Dispatches and Dispatches Summary),Configurations (Dispatch Documents)

5. System Configuration: Country, State, Cities, County, Transportation, Entities, Product, Locations, Services, Trucks.

6. Billing: List, Reports, Bill Summary

7. Security: Login User Account, Clients Accounts

These functionalities were exactly what the client needed to spearhead their international initiatives. The Chilean client and Chetu will continue to collaborate on additional development. Despite being geographically distanced, we were able to progress without any roadblocks, a painless and seamless partnership we hope to continue.

The multi-language capabilities supported international scalability; the international measuring units, web-based, and cloud-based features fostered a growing consumer network. They have seen a boost in sales and managed to decrease human-error.

technology community management software with logistics management
Let's Work Together

Contact us to learn more about Chetu and our custom software services

Privacy Policy | Legal Policy | Careers | Sitemap | Referral | Contact Us

Chetu Limited is a company registered in England and Wales with company number 11882245

Copyright © 2000- Chetu Inc. All Rights Reserved.

Button to scroll to top

By continuing to use this website, you agreeto our cookie policy. GOT IT