I'm building a SaaS product and having doubts on how to organise the navigation and interaction in a user records flow.

The flow consists of a stock transaction record and the document objects are supposed to be stored forever.

In my application menu, I have three elements:

  • Remove From Stock
  • Add To Stock
  • Show Stock Transactions

Both Remove From Stock and Add To Stock will open an input page where the user will select the stock item article, description and quantity and a new record is added to database. Date/Time and type (added/removed) fields are added automatically. The latest added field is shown in screen after commit.

The Show Stock Transactions option will show all of my transactions over time. I've opted to use a date filter instead of pagination, as the following example:

enter image description here

The user can select a specific date range (Today, Yesteday, etc.) or choose to type specific dates on the FROM and TO inputs.

In practice, this approach is getting "complaints" from the following points:

a) When adding new transactions, I should be switching screens on the menu. b) Every time I add a new transaction, I have to switch to "Show Stock Transactions" to see the added record. The added record is not easily visible on screen. c) There is no clone buttons. I need to be able to clone a previous transaction, no matter how old it is.

I kindly ask for suggestions on how to improve the usability of the flow and the navigation.

  • Hi Mendes. Can you please show us all the screens that the user is interacting with. Is add a stock a transaction? Why isn't the added record easily visible? – Mircea Anton Jun 3 '19 at 12:28
  • Add a stock and Remove from stock are all transactions and both are simple input screens. – Mendes Jun 3 '19 at 13:03
  • 1
    Ok. How do these screens show? are they pop-ups on a home/landing page, or are they individual pages that are loaded? Where does the menu sit when switching between screens? And why do you have to switch screens from the menu when adding new transaction, I assume you should be focused on entering the data for the new transaction. Thanks. – Mircea Anton Jun 3 '19 at 13:16
  • The menu sits in the top header (top menu). The input screens are individual pages. So to enter some data the user selects the option on the top menu and then an input page appear. When concluding the new added record is shown in screen. – Mendes Jun 3 '19 at 13:54
  • After adding a new record you are showing the stock transaction page right? That page is the image that you have attached to your post? – Mircea Anton Jun 3 '19 at 14:26

enter image description here

HI Mendes, here's what I had in mind.

The default page is the Transaction page. Because this is the most relevant information for the user. You have two buttons: Add to stock and Remove from stock at the bottom of the table.

You don't need to show the detail page for the item after submitting it. You will show the transaction page with the highlighted new entry.

Once you click on the entry or refresh the page the 'new entry' highlight disappears.

If you wish to see details of the transactions you double click on them and you will show a pop up.

You add an extra row for selecting the entries. If you select an entry then the duplicate entry button shows/activates.

The table entries could be fixed height with a scroll or you could have an infinite scroll with the add remove buttons being sticky.

enter image description here enter image description here enter image description here

Hope this helps.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.