This type of data-drive setup can drive a less-skilled maintenance programmer bonkers. I'm moderately skilled at Perl, and it took me several minutes, and most of the fingers on one hand, to puzzle out what you were trying to do.

Let me suggest an alternate approach. First get rid of the opendir calls by delegating to File::Find. 

  use File::Find;

  find(\&eachfile, "/data/");

[download]
and then structure the callback along the lines of 
  sub eachfile {
      my $path = $File::Find::name;

      return if -d $path;

      $path =~ s|^.*/(.+)_logs/|| or return; # or log
      my $item = $1;

      if ( $path =~ m|(.+)\.(\d+)$| ) {
          my($company,$quantity) = ($1,$2);
          inventory($company, $item, $quantity);
          return;
      }

      # and so on for each remaining case

      # eventually logging any that you can't handle
  }

[download]
That's the rough idea, at least -- it needs some cleanup and error handling.

This would seem to me to be a very easy thing for whoever comes along after you to understand and maintain. The most they would need to understand is File::Find, and that's a low hurdle.

Granted, this leaves you with the equivalent of a string if/elseif*/else, but it seems easy enough to follow.

In reply to Re: The dreaded if-elsif-else construct (code) by dws
in thread The dreaded if-elsif-else construct (code) by deprecated

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.