Add new accounts more easily

In our continued efforts to make Seller Ledger easier to use, we rolled out some improvements to how accounts are linked and displayed on the Dashboard page

The first thing you might notice is that, if you have multiple accounts from the same sales channel or bank, they are now grouped more obviously together:

But the biggest change is the addition of the new “plus” icon within each channel/bank header:


Clicking this icon allows you to quickly add another account from that same bank or sales channel.

To add a new sales channel, or accounts from a new bank or credit card, you would still click the button below your accounts, now more accurately labeled “Add Channels & Banks”

As always, we welcome feedback on our product changes, so feel free to email us at [email protected]

Import Whatnot sales history into Seller Ledger

We are excited to announce that Whatnot sellers can now import their “ledger” details into Seller Ledger.

While Whatnot does not yet provide a public API (which means we can’t automatically grab your transaction history like we can with Amazon, eBay, Etsy and Shopify,) they did release the ability to export ledger details in CSV format earlier this spring. We can import these files directly into Seller Ledger, like we do for both Poshmark and Mercari.

Step 1: Download your Whatnot sales history

Go to Seller Hub, under Financials, and then under Ledger – you should see an option to export your history in a CSV formatted file. Go ahead and download and save that file.

Step 2: Add a Whatnot account in Seller Ledger

When you click the “Add account” button under Connected Accounts on your Seller Ledger dashboard, you will now see an option to “Connect to Whatnot.”


After clicking the Whatnot button, enter a name for your new account and click “Create Account”

Step 3: Upload your Whatnot ledger file

Once you’ve created your new Whatnot account, you’ll be taken directly into that new account, to a screen that allows you to upload your Whatnot ledger file. Choose the file you downloaded from Whatnot and click “Save.” Your file will be uploaded and your transaction history will be imported into Seller Ledger.

Trial users

If you are still in your trial period, Seller Ledger will only import the last 90 days of transaction history, regardless of how large your Whatnot file is.

Step 4: Categorize your Whatnot payouts properly

Whatnot currently pays sellers via Stripe (often to a bank account) and PayPal. If you link your bank or PayPal account to Seller Ledger, you’ll want to make sure that your payouts from Whatnot don’t get double-counted. So, when you see your Whatnot payouts hit your bank or PayPal account, make sure to categorize them as “Transfer: My Whatnot Sales” – or whatever you named your Whatnot account.

Step 5: Remember to regularly update your Whatnot sales in Seller Ledger

Because we can’t pull in your new sales and expense information on a dailybasis, you’ll want to make sure to come back every once in a while to upload your latest sales history. How often you choose to do so is your choice. We show the date of the most recent imported transaction on the Seller Ledger dashboard to help remind you.

Lastly, if you make a mistake with any of your uploaded information, it’s not a problem. The “Import History” tab shows you all of the files you’ve uploaded over time, with the ability to simply delete one or more and try again.

New to Seller Ledger?

We know there are other channels out there that provide CSV files of transaction history. If you would like to see other channels supported, please request a new platform or email us at [email protected] with your interest and, if you’d like to be particularly helpful, a sample of a transaction history file from that channel.


The Seller Ledger Team

Add inventory costs from receipts

In our continuing efforts to make eCommerce accounting easier, today we announce a big step forward for inventory tracking.

In short, you can now take a picture of your receipt and upload it to Seller Ledger. We use the latest “artificial intelligence” technology to extract item cost information from the image and pre-populate the inventory purchase form.

To show you exactly what’s possible, here is a picture, taken from an iPhone, of a receipt from a trip to our local Marshall’s store:

Within Seller Ledger, if this purchases came in from a linked bank or credit card, make sure to categorize it as “inventory” and then go to Inventory -> Purchases and click “Add details.” If this was a cash purchase, or from a source not connected to Seller Ledger, just go to this same screen and click the “Add Inventory” button.

You will see a new option at the bottom of the screen to “Upload image or pdf”:

upload inventory from receipt

Click the “Upload receipt” button and choose the picture that you took of your receipt (or try the example we’ve posted above.) Seller Ledger will then process the image and extract as much information as possible. In the above example, you will end up with the following:

And scroll down to see the remaining information that we were able to extract from the image…

Notice that we found 4 unique items with descriptions and the correct per-item costs. Not only that, but we were able to recognize the $6.32 in sales tax. And given our recent feature that allocates extra cost of goods amounts, we automatically allocated that $6.32 across the 4 items.

The one piece of work left for you to complete is to either identify or create the unique SKU for each item, which will then allow Seller Ledger to match to sold items, thereby updating inventory and cost of goods amounts automatically when it sells.

To help us improve this feature over time, it helps to get as may customers trying it as possible. Please give it a try and let us know how we can make it better.

Automatically allocate other charges to cost of goods

When you purchase inventory, there are often other costs besides the cost of the individual items that must be accounted for as part of “cost of goods.” In fact, we wrote a blog post about it a while back.

Until now, deciding how to handle those extra costs was something that customers had to figure out on their own. Well, no more. Now, Seller Ledger allows you to enter those additional costs and we automatically adjust the per-item cost of goods for your inventory.

You will now see a new “Other costs” field at the top of the form for entering inventory purchase details. Enter the total of any extra costs paid, be it sales tax, inbound shipping, processing fees, whatever. Then, as you record the item-level purchase details, you will see the “other costs” amount divvied up among the items, based on the weighted average cost of those items within the overall purchase.

This feature saves you time so you don’t have to attempt any calculations yourself. And it sets us up well to support the next big feature we’re working on: the ability to upload a picture of a receipt and have us create inventory purchase details from it. Stay tuned.

Know which items make you the most profit

To really understand how to improve your eCommerce business, you should know which items make you the most profit. Seller Ledger recently rolled out summary-level gross margin totals on the dashboard of those sellers who track inventory. Now, we have introduced a new “gross profit” report to show you that same information (and more) on a per-item level.

Just go to the Reports tab, and choose the new “Gross Profits” sub-tab:

For each unique item that you sell, we will show you how much total gross profit you make, as well as your average gross margin for those items. You can sort by different columns too. This allows you to see which items make you the most profit for your business. Hopefully, this information can help inform your sourcing strategies going forward.

Better cost tracking = better information

It’s important to realize that this report is only going to be as helpful as the information you’ve entered into Seller Ledger. The more “cost” information you provide about your inventory, the more accurately we can report on your sales and profits.

Pro tip

One of the quickest ways to load inventory cost information into Seller Ledger is to upload it in CSV format. Check out our blog post on how to do just that.

For those of you who may be using the cash-based approach to inventory, or simply tracking at the balance level, this new report won’t be particularly useful. But, in case this might motivate you to track at a more detailed level, feel free to go back and see how Seller Ledger can support you.

Help us further automate inventory costs

We continue to look for ways to reduce the amount of effort required to get what you need out of Seller Ledger. And we understand that tracking inventory is one of the most challenging aspects of running an eCommerce business. As such, we’d love to hear suggestions on ways to improve the ability to get inventory cost information into our platform.

Please email us at [email protected] with your suggestions and we’ll do our best to tackle as many as we can.

Switching from QuickBooks to Seller Ledger: Mileage

Are you thinking of switching from QuickBooks to Seller Ledger but are worried about losing historical data? Well, it turns out that we have started making it easy to take your QuickBooks transaction information and bring it over.

Mileage trips

We just built a simple tool to import all of your QuickBooks mileage history into Seller Ledger. All you need to do is export your trip history in a CSV format. Working with a customer recently, we found that the QuickBooks mileage file contains the following columns:

  • Date
  • Type
  • Trip Purpose
  • Vehicle
  • Start Address
  • End Address
  • Distance
  • Deduction
  • Logging Method

Now, because Seller Ledger is designed for small businesses who file a Schedule C, we don’t require as much information to be tracked. For example, we only care about “Business” trips, so don’t ask for a “Type” value (e.g. Business or Personal.) We also don’t ask you which vehicle you’re using. In fact, we only require the minimum information necessary to calculate your IRS standard mileage deduction:

  • Trip date
  • Description
  • Distance

Seller Ledger knows the right mileage rate based on your trip date, and we let you decide how you wish to calculate the distance drive.

In fact, if you send us a CSV file that includes value for just those 3 columns, we’ll be happy to help upload the data for you.

Is this a feature?

At the moment, we don’t have this functionality as a customer-facing feature within the application. In fact, our customer support team built a simple tool using our recently introduced API (which stands for “application programming interface.) For any technical users who might be interested, we published a step-by-step tutorial on exactly how to build such a tool.

So if your want to switch from QuickBooks to Seller Ledger, and could use help with your mileage information, shoot us an email at [email protected] and we’ll be happy to help.

And stay tuned for future updates on other ways to help you switch:)

View your top selling products across all channels

Want to know which products sell the most across all of your eCommerce channels? With Seller Ledger’s new “Product Sales” report, you’re just a couple of clicks away. Simply go to the Reports tab and click the “Product Sales” sub-tab and, voila:

Stay tuned for more updates as we continue to work on providing better insight into your eCommerce business. And please keep passing along suggestions on how we can do better.

API Tutorial: Build a simple web app to load mileage trips into Seller Ledger

To prove how easy it is to use Seller Ledger’s (brand) new API, we’ve thrown together a super lightweight web application that even a novice programmer could replicate.

Goal: create a way to load mileage data into a Seller Ledger account

As a simple use case, let’s take a request we’ve heard from a number of customers – how can I import mileage transactions that I have tracked elsewhere? Given that a number of mobile mileage trackers provide trip data in CSV format, we decided to create the simplest tool we could think of: a single web form where you can copy and paste some mileage data in CSV format and send it to your Seller Ledger account.

We’ll be doing this using Ruby on Rails as the framework for this tutorial.

Step 1: Learn how to access a Seller Ledger account

Looking at the documentation for Seller Ledger’s API, you can see that all you need to get started is an api token…

which can be found under the new Settings -> API sub-tab (that the docs link to.)


Please be aware – the API token in the above screen shot is fake – it is not tied to a real account. Throughout this tutorial, you will need to use an actual Seller Ledger API token for this example to work.

Step 2: Learn what information Seller Ledger expects in order to load mileage transactions

Looking again at the API documentation, creating a mileage transaction requires only 3 pieces of information and describes the format required:

  1. Date of the trip
  2. A description of the trip
  3. Distance traveled

You don’t need to know the current IRS mileage rate . Seller Ledger has that information and does the calculation based on the date of the trip.

Step 3: build the simplest way to capture the information needed to load mileage data into Seller Ledger

So, it appears that we only need two type of information to update Seller Ledger with mileage data – an authentication token and the raw trip data itself. Let’s put that to the test. Time to start a new rails application:

rails new test-sl-mileage-app

Fortunately, Seller Ledger has published a Ruby gem to help develop against its API. The source code for that gem, and it’s readme is published on GitHub. Looking at the readme instructions, I can install that gem. Let’s go into the directory of our new rails app

cd test-sl-mileage-app/

and add the gem to our project

bundle add seller_ledger-ruby

Now, let’s do some blocking and tackling to get a page where you can enter the info. These are steps specific to building a lightweight rails app, so feel free to skip ahead if you’re already familiar. Let’s create a new “home” controller – which will be the only one we’ll need (and apologies in advance for not using proper design patterns:)

rails g controller home

Now, go update your routes file and edit the default root_url route:

change #root "articles#index" to root "home#index"

Make sure to add the index method to home_controller.rb

def index 

Now it’s time to build the actual HTML page at home#index to capture the important information. To keep things simple, include a single text box to request the API token, and a text field box where a user could paste in (or type, if s/he so desires) a bunch of csv data. Create a new view file under the home folder, called index.html.erb. And add the following basic HTML:

<h1>A Simple Mileage Loading app for Seller Ledger</h1>

<%= form_with url: "/load", method: :post, data: {turbo: false} do |form| %>
    <p><%= form.label "Seller Ledger API Token:" %><p>
    <p><%= form.text_field :token %></p>
    <p><%= form.label :data, "Enter mileage data:" %></p>
    <p><%= form.text_area :data, size: "70x5" %></p>
    <p><%= form.submit "Submit" %></p>
<% end %>

Voila – we see the following completely un-styled, yet potentially functional web page. This should allow us to capture the information needed to load multiple mileage trips into Seller Ledger

Before moving on to the next phase, add a route for that form’s post action in our routes.rb file. To keep things simple, we will put everything in the “home” controller.

post "load" => "home#load", :as => "load"

Step 4: Take the information from the web form, and push it into Seller Ledger

An easy first step here is to create a single Ruby service object (a PORO – or “plain old ruby object”) that takes an API token, initializes itself with it. The service object can then have a method that takes the raw csv data passed to it, parses it, and sends it to Seller Ledger. Create a “services” directory under the “app” folder and, inside that new folder, and create a new file. In this tutorial, we’re calling our object “Parser” and naming the file parser.rb.

class Parser


Now it’s time to create mileage transactions within Seller Ledger, so let’s take a look at that API documentation again.

Add the ‘require’ statement at the beginning of the object file. Also, create an initialize method that takes an API token as it’s parameter and creates a new Seller Ledger api client that can be used by the rest of our Parser object:

def initialize(token)
    @client =

To see if this is working, let’s open ‘rails c’, create a token variable and see if we can initialize our new Parser object with it:

irb(main):001> token = 'SL_PRD_acbdef12acbdef12acbdef12acbdef12'
=> "SL_PRD_acbdef12acbdef12acbdef12acbdef12"
irb(main):002> p =

Bingo! Now, what’s the simplest thing we can test to see if our code is actually talking to Seller Ledger? Well, “Get all Mileage transactions” looks pretty straightforward:

Now let’s add a quick method to our Parser.rb file.

def list_mileage

And we’ll try this again.

irb(main):001> token = 'SL_PRD_acbdef12acbdef12acbdef12acbdef12'
=> "SL_PRD_acbdef12acbdef12acbdef12acbdef12"
irb(main):002> p =
irb(main):003> p.list_mileage

Alrighty! Our lightweight web app is talking directly to Seller Ledger. Now, let’s add a “load” method in the “home” controller with some logic to grab the form data and get it ready to send to our Parser object:

def load
    token = params[:token]
    data = params[:data]
    p =
    @result = p.load(data)

We’re grabbing the token value from the form field and passing it in when we initialize the Parser object. We then grab the actual csv data from that form field and pass it to a new method that we’ll call “load”. And we’ll store the response from that method in an instance variable that we can show in the view.

Now, we just need to create that new “load” method in Parser.rb to grab the csv data, actually parse it, iterate over it, and pass the values into Seller Ledger:

def load(data)

    keys = ["trip_date", "description", "distance"]
    results = []
    data.each_line do |line|
        results << @client.create_mileage_transaction(Hash[","))])
    return results

The approach used here was to create keys and build a hash using them for each line of input. We further assume no header information is provided in the CSV data, just the raw trip information. However, while iterating over the raw csv data, you could just as easily assign the parameters to pass into Seller Ledger individually like in the documentation.

Finally, let’s create a load.html.erb view file to show the returned results:


<%= @result %>

Step 5: try it out

Go ahead and enter some simple csv formatted data into that web form, along with your API token (remember to use your actual token, not this fake one:)

Hit “Submit” and….

Looks like we got a result with rates and calculated deduction amounts. Let’s check our Seller Ledger account’s Mileage transaction view:

There you have it. A super simple web app to load multiple mileage trips into Seller Ledger. It actually took far less time to create the app than it did to write this tutorial.

Help us expand the API

We’re very eager to hear from other developers what we can do to make our API better and more valuable. Email us your ideas at [email protected] or fill out the brief form on our API page.

eCommerce Accounting API is here

In the spirit of encouraging more automation in the world of eCommerce accounting, Seller Ledger is announcing the launch of a new API (application programming interface.) This will allow third party developers to further extend their product functionality by making it easy to interact with Seller Ledger.

What can I do with an API?

To provide one illustration, let’s take a look at the mileage deduction. There are many third party apps (a lot of them mobile) that do a good job of tracking the miles you drive for your business, but getting that information into your accounting platform can be challenging. Seller Ledger’s first API endpoint allows anyone to upload and access their mileage trips.

We will be expanding support for more areas of eCommerce accounting and welcome suggestions from developers near and far. Please let us know what else you’d like to see.

See it in action

We have designed our API to allow developers to be as productive as possible, as quickly as possible. To demonstrate, our founder built a simple web application and documented his experience.

Start exploring for yourself

Feel free to check out our documentation to learn more about how you can start extending functionality.

Automate your Shopify accounting with Seller Ledger

The Seller Ledger team is pleased to announce that we now connect directly with your Shopify Store to help automate much of your eCommerce business accounting. As with eBay, Amazon and Etsy, you can link your Shopify store(s) to Seller Ledger and we’ll regularly import your sales and expenses and automatically categorize them for you. Just log into your dashboard and click the “Add Account” button to link your Shopify store.

The flow is a bit different for Shopify than it is for connected marketplaces. After clicking on the button to “Connect to Shopify”, you will be taken to Seller Ledger’s listing on the Shopify App Store. Click the button to “Install” our app, and you will redirected back to Seller Ledger once the connection and proper permissions have been established.

Also, like with eBay, Amazon and Etsy, you can always change how you’d like to see your Shopify information categorized by customizing your settings.

What if I already sync eBay and Amazon with Shopify?

We do know that some users have chosen to sync their eBay and Amazon sales and product information with their Shopify store. But fear not, we only import Shopify store-specific sales from Shopify and ignore any other information from other platforms. To get data from multiple channels, you will need to connect to each channel directly. We do this to maximize the granularity and accuracy of the underlying data, as well as to avoid duplicate entries.

Thanks go out to the current Seller Ledger customers who helped us beta-test the integration with Shopify. If you are a Shopify customer and like the continued automation we’re providing, please consider helping us out with a review on the listing page. It’s a terrific way to help get the word out.